I'm reporting this as an issue but in fact it requires more investigation (which unfortunately I'm not able to perform at this time).
- configure Kafka for consistency, for example:
- run Connect for the first time, which should create its internal topics
I believe these topics are created with the broker's default, in particular:
but connect doesn't produce with acks=all, which in turn may cause the cluster to go in a bad state (see, e.g., https://issues.apache.org/jira/browse/KAFKA-4666).
Solution would be to force availability mode, i.e. force:
when creating the connect topics, or viceversa detect availability vs consistency mode and turn acks=all if needed.
I assume the same happens with other kafka-based services such as streams.