kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ewen Cheslack-Postava (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-4667) Connect should create internal topics
Date Wed, 19 Apr 2017 16:51:41 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ewen Cheslack-Postava updated KAFKA-4667:
         Priority: Critical  (was: Major)
    Fix Version/s:

Also increasing priority and optimistically setting the fix version to 0.11 since this issue
has affected quite a few people now.

> Connect should create internal topics
> -------------------------------------
>                 Key: KAFKA-4667
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4667
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>            Reporter: Emanuele Cesena
>            Priority: Critical
>             Fix For:
> 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

View raw message