These messages are usually caused by leader migration. I think as long as you don¹t see this lasting for ever and got a bunch of under replicated partitions, it should be fine.
Jiangjie (Becket) Qin On 2/25/15, 4:07 PM, "Zakee" <kzak...@netzero.net> wrote: >Need to know if I should I be worried about this or ignore them. > >I see tons of these exceptions/warnings in the broker logs, not sure what >causes them and what could be done to fix them. > >ERROR [ReplicaFetcherThread-3-5], Error for partition [TestTopic] to >broker >5:class kafka.common.NotLeaderForPartitionException >(kafka.server.ReplicaFetcherThread) >[2015-02-25 11:01:41,785] ERROR [ReplicaFetcherThread-3-5], Error for >partition [TestTopic] to broker 5:class >kafka.common.NotLeaderForPartitionException >(kafka.server.ReplicaFetcherThread) >[2015-02-25 11:01:41,785] WARN [Replica Manager on Broker 2]: Fetch >request >with correlation id 950084 from client ReplicaFetcherThread-1-2 on >partition [TestTopic,2] failed due to Leader not local for partition >[TestTopic,2] on broker 2 (kafka.server.ReplicaManager) > > >Any ideas? > >-Zakee >____________________________________________________________ >Next Apple Sensation >1 little-known path to big profits >http://thirdpartyoffers.netzero.net/TGL3231/54ee63b9e704b63b94061st03vuc
