Anyone ? We really hit the wall deciphering this error log, and we don't know how to fix it.
On Wed, Oct 10, 2018 at 12:52 PM Raghav <raghavas...@gmail.com> wrote: > Hi > > We are on Kafka 1.1 and have 3 Kafka brokers, and help your need to > understand the error message, and what it would take to fix the problem. > > On Broker-1 we see the following logs for several and *some producers > fails to write to Kafka*: > > [2018-10-08 12:28:25,609] INFO [ReplicaFetcher replicaId=1, leaderId=3, > fetcherId=0] Remote broker is not the leader for partition > __consumer_offsets-44, which could indicate that the partition is being > moved (kafka.server.ReplicaFetcherThread) > [2018-10-08 12:28:25,609] INFO [ReplicaFetcher replicaId=1, leaderId=3, > fetcherId=0] Remote broker is not the leader for partition > __consumer_offsets-20, which could indicate that the partition is being > moved (kafka.server.ReplicaFetcherThread) > [2018-10-08 12:28:25,609] INFO [ReplicaFetcher replicaId=1, leaderId=3, > fetcherId=0] Remote broker is not the leader for partition > __consumer_offsets-2, which could indicate that the partition is being > moved (kafka.server.ReplicaFetcherThread) > > Here is server.properties on Broker-1 > > *# The id of the broker. This must be set to a unique integer for each > broker. > broker.id <http://broker.id>=1* > *auto.create.topics.enable=true > > delete.topic.enable=true* > * > > ################ SHUTDOWN and REBALANCING > ####################### > # Both the > following properties are also enabled by default as well, also explicitly > settings here* > *controlled.shutdown.enable=true > > auto.leader.rebalance.enable=true* > *unclean.leader.election.enable=true* > > > -- > Raghav > -- Raghav
