Kevin Lewis

Maybe. I think I've seen it to some degree in Keyster, it has two topics, each with 32 partitions.

@rawkode I think that will happen any time the messages in the topic that tracks the offsets (which is internal to Kafka) expires before the messages themselves. There may be...

@besteman Interesting, I've not seen a problem in that area before. Are you sure the certificate is valid? Wonder if you could generate a new one just as a test...

@sheshankkodam The approach we've used is to just create the topics prior to usage. This seems to always be what we want in any case. Would this work in your...

Yes, I do see what you mean. What we do is have an init script that creates the topics when the Docker container starts. So we still only do `docker-compose...

@reachfh Thank you very much! Kaffe could really use some SSL refactoring. I haven't had time to look at your PR in any depth, but I did note your mention...

Maybe we can rework the config for the next major revision.

What does having a separate consumer group per topic provide? The consumer group is still specific to the topic.

Yes, if you're consuming from the same topic multiple times, two consumer groups would be necessary. However, I don't think consuming from two different clusters would necessitate different consumer groups....

> Well, it's an issue, because (correct me if I'm wrong) but kaffe can only setup one message handler, so you've got one handler for both data and instruction topics,...