kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emanuele Cesena (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-4667) Connect (and Stream?) should create internal topics with availability or consistency properly set
Date Tue, 17 Jan 2017 22:39:26 GMT
Emanuele Cesena created KAFKA-4667:
--------------------------------------

             Summary: Connect (and Stream?) should create internal topics with availability
or consistency properly set
                 Key: KAFKA-4667
                 URL: https://issues.apache.org/jira/browse/KAFKA-4667
             Project: Kafka
          Issue Type: Bug
            Reporter: Emanuele Cesena


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).

Repro steps:
- configure Kafka for consistency, for example:
default.replication.factor=3
min.insync.replicas=2
unclean.leader.election.enable=false
- 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:
min.insync.replicas=2
unclean.leader.election.enable=false
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:
unclean.leader.election.enable=true
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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message