I had this issue lately.
On broker 9. Check what errors you got from a change log:
kafka-run-class kafka.tools.StateChangeLogMerger --logs
/var/log/kafka/state-change.log --topic [__consumer_offsets
If it complains about connection, it maybe this broker does not read data from
zookeeper
Check zookeeper for this topic – number of partition.
If it there correctly, restart the broker.
On 12/21/16, 11:49 PM, "Stephane Maarek" <steph...@simplemachines.com.au> wrote:
Hi,
I’m doing a repartitioning from broker 4 5 6 to broker 7 8 9. I’m getting a
LOT of the following errors (for all topics):
[2016-12-22 04:47:21,957] ERROR [ReplicaFetcherThread-0-9], Error for
partition [__consumer_offsets,29] to broker
9:org.apache.kafka.common.errors.NotLeaderForPartitionException: This
server is not the leader for that topic-partition.
(kafka.server.ReplicaFetcherThread)
1) Is that bad?
2) why is it happening? I’m just running the normal reassign partition tool…
I’m getting this with kafka 0.10.1.0
Regards,
Stephane
----------------------------------------------------------------------
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, notify the sender immediately by return email and delete the message
and any attachments from your system.
