[
https://issues.apache.org/jira/browse/KAFKA-10890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255473#comment-17255473
]
GeoffreyStark commented on KAFKA-10890:
---------------------------------------
controller log has been follow text
!image-2020-12-28-16-59-03-492.png!
> Broker just stated Ignoring LeaderAndIsr request from controller
> -----------------------------------------------------------------
>
> Key: KAFKA-10890
> URL: https://issues.apache.org/jira/browse/KAFKA-10890
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0
> Environment: kfk 2.0
> 74 brokers
> 3 replica-factors
> Reporter: GeoffreyStark
> Priority: Major
> Attachments: image-2020-12-28-16-59-03-492.png,
> jstack-1013broker-1228-1312, kafka元数据混乱.docx
>
>
> In auto.leader.rebalance.enabled=true
> Taking a Broker 1013 (with many leader partitions) offline；
> Then, after the leaders of these subdivisions have been elected from other
> ISRs,
> In theory, 1013 should once again become the leader of those partitions
> Indeed, if you look at the describe command and the information of the
> corresponding partition in ZK, you can see that the leader has changed back
> to 1013.
> But if you look at the Controller log and the 1013 log at this point, you'll
> see that there are some warning messages, and after a while,
> the producer reports an error"
> The server is not the leader for that topic-partition..Going to request
> metadata update now
> "
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
