kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yeva Byzek (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-5666) Need feedback to user if consumption fails due to offsets.topic.replication.factor=3
Date Thu, 27 Jul 2017 17:07:00 GMT
Yeva Byzek created KAFKA-5666:
---------------------------------

             Summary: Need feedback to user if consumption fails due to offsets.topic.replication.factor=3
                 Key: KAFKA-5666
                 URL: https://issues.apache.org/jira/browse/KAFKA-5666
             Project: Kafka
          Issue Type: Improvement
            Reporter: Yeva Byzek


Introduced in 0.11: The offsets.topic.replication.factor broker config is now enforced upon
auto topic creation. Internal auto topic creation will fail with a GROUP_COORDINATOR_NOT_AVAILABLE
error until the cluster size meets this replication factor requirement.

Result: Default is setting offsets.topic.replication.factor=3, but in development and docker
environments where there is only 1 broker, the offsets topic will fail to be created when
a consumer tries to consume and no records will be returned.

Issue: the user experience is bad.  The user may have no idea about this setting change and
enforcement, and they just see that `kafka-console-consumer` hangs with ZERO output. 

Suggestion: consider giving feedback to the user/app if offsets topic cannot be created. 
For example, after some timeout.

Workaround:
Set offsets.topic.replication.factor=3





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message