Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Fri, 12 Aug 2016 22:09:20 +0000 (UTC)
From: "Onur Karaman (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12989057.1468401168000.296684.1471039760995@Atlassian.JIRA>
In-Reply-To: <JIRA.12989057.1468401168000@Atlassian.JIRA>
References: <JIRA.12989057.1468401168000@Atlassian.JIRA> <JIRA.12989057.1468401168734@arcas>
Subject: [jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of
 replicas at startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 12 Aug 2016 22:09:23 -0000


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

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

[~granthenke] maybe in the long term. But honestly I would prefer the simple, quick fix for this edge case behavior without complicating the conversation with KIP-73 and KIP-46. To me, the cluster not meeting replication factor requirements on an internal topic is another way of saying the cluster isn't fully setup yet.

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