[ https://issues.apache.org/jira/browse/KAFKA-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manikumar resolved KAFKA-4027. ------------------------------ Resolution: Duplicate This behavior is changed in KAFKA-5758. Please reopen if you think the issue still exists in newer versions. > Leader for a cetain partition unavailable forever > ------------------------------------------------- > > Key: KAFKA-4027 > URL: https://issues.apache.org/jira/browse/KAFKA-4027 > Project: Kafka > Issue Type: Bug > Components: core > Affects Versions: 0.10.0.0 > Reporter: tu nguyen khac > Priority: Major > > I have a cluster of brokers ( 9 box) , i 'm naming it from 0 --> 8 . > Yesterday some servers went down ( hard reset ) i regularly restart these > server ( down servers ) but after that some topics cannot assign leader > i checked server log and retrieved these logging : > kafka.common.NotAssignedReplicaException: Leader 1 failed to record follower > 6's position -1 since the replica is not recognized to be one of the assigned > replicas 1 for partition [tos_htv3tv.com,31]. > at > kafka.cluster.Partition.updateReplicaLogReadResult(Partition.scala:251) > at > kafka.server.ReplicaManager$$anonfun$updateFollowerLogReadResults$2.apply(ReplicaManager.scala:864) > at > kafka.server.ReplicaManager$$anonfun$updateFollowerLogReadResults$2.apply(ReplicaManager.scala:861) > at > scala.collection.immutable.HashMap$HashMap1.foreach(HashMap.scala:221) > at > scala.collection.immutable.HashMap$HashTrieMap.foreach(HashMap.scala:428) > at > kafka.server.ReplicaManager.updateFollowerLogReadResults(ReplicaManager.scala:861) > at kafka.server.ReplicaManager.fetchMessages(ReplicaManager.scala:470) > at kafka.server.KafkaApis.handleFetchRequest(KafkaApis.scala:496) > at kafka.server.KafkaApis.handle(KafkaApis.scala:77) > at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:60) > at java.lang.Thread.run(Thread.java:745) > i tried to run Prefered Leader but it didn't work ( some partitions has node > leader ) :( -- This message was sent by Atlassian JIRA (v7.6.3#76005)