You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Michael Taranov (JIRA)" <ji...@apache.org> on 2017/05/08 08:42:04 UTC
[jira] [Created] (KAFKA-5193) Kafka broker service failed to stop
with many NotLeaderForPartitionException exceptions
Michael Taranov created KAFKA-5193:
--------------------------------------
Summary: Kafka broker service failed to stop with many NotLeaderForPartitionException exceptions
Key: KAFKA-5193
URL: https://issues.apache.org/jira/browse/KAFKA-5193
Project: Kafka
Issue Type: Bug
Components: core
Affects Versions: 0.10.2.0
Environment: CentOS Linux release 7.2.1511 (Core)
kafka-0.10.2.0
Reporter: Michael Taranov
Attachments: kafka_broker_dump_201705072032.txt
Kafka broker failed to stop while generating a lot of {{NotLeaderForPartitionException}} in {{server.log}} for all topics.
{noformat}[2017-05-07 20:08:48,322] ERROR [ReplicaFetcherThread-0-15], Error for partition [topic1,83] to broker 15:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-05-07 20:08:48,322] ERROR [ReplicaFetcherThread-0-15], Error for partition [topic2,10] to broker 15:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-05-07 20:08:48,362] ERROR [ReplicaFetcherThread-0-9], Error for partition [topic,20] to broker 9:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread){noformat}
On {{service kafka stop}} it removed pid but broker process was still up.
Only {{kill -9}} helped.
Attached thread dump
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)