[ 
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419057#comment-15419057
 ] 

Onur Karaman commented on KAFKA-3959:
-------------------------------------

Perfect timing! [~toddpalino] and I hit this behavior again on Wednesday after 
reset one of our test clusters. The current behavior came from KAFKA-1864.

The current behavior is pretty surprising when you have clients or tooling 
running as the cluster is getting setup. Even if your cluster ends up being 
huge, you'll find out much later that __consumer_offsets was setup with no 
replication.

I think the right behavior should be for __consumer_offsets topic creation to 
fail with {{GROUP_COORDINATOR_NOT_AVAILABLE}} until there are at least 
{{KafkaConfig.offsetsTopicReplicationFactor}} brokers up in the cluster.

> __consumer_offsets wrong number of replicas at startup
> ------------------------------------------------------
>
>                 Key: KAFKA-3959
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3959
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer, offset manager, replication
>    Affects Versions: 0.9.0.1, 0.10.0.0
>         Environment: Brokers of 3 kafka nodes running Red Hat Enterprise 
> Linux Server release 7.2 (Maipo)
>            Reporter: Alban Hurtaud
>
> When creating a stack of 3 kafka brokers, the consumer is starting faster 
> than kafka nodes and when trying to read a topic, only one kafka node is 
> available.
> So the __consumer_offsets is created with a replication factor set to 1 
> (instead of configured 3) :
> offsets.topic.replication.factor=3
> default.replication.factor=3
> min.insync.replicas=2
> Then, other kafka nodes go up and we have exceptions because the replicas # 
> for __consumer_offsets is 1 and min insync is 2. So exceptions are thrown.
> What I missed is : Why the __consumer_offsets is created with replication to 
> 1 (when 1 broker is running) whereas in server.properties it is set to 3 ?
> To reproduce : 
> - Prepare 3 kafka nodes with the 3 lines above added to servers.properties.
> - Run one kafka,
> - Run one consumer (the __consumer_offsets is created with replicas =1)
> - Run 2 more kafka nodes



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

Reply via email to