kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jun Rao <jun...@gmail.com>
Subject Re: kafka availability
Date Fri, 04 Apr 2014 14:48:06 GMT
That part is fine. Only one of the brokers will become the controller. If
the controller already exists and another broker tries to become the
controller, it will see the conflict. Do you see broker 0 registered under
/brokers/id path in ZK? If so, you need to figure out why broker 0 is not
part of the isr. Any error in the controller/state-change log? Could you
check the maxLag and minFetch bean ReplicaManager in broker 0 (



On Fri, Apr 4, 2014 at 7:14 AM, Anatoly Deyneka <adeyneka@gmail.com> wrote:

> Yes, broker 0 is started.
> INFO conflict in /controller data: { "brokerid":0,
> "timestamp":"1396619945779", "version":1 } stored data: { "brokerid":1,
> "timestamp":"1396511882085", "version":1 } (kafka.utils.ZkUtils$)
> INFO [Kafka Server 0], Started (kafka.server.KafkaServer)
> if the problem is conflict I guess log level should be at least warn.
> How to solve this conflict?
> Anatoly

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message