[
https://issues.apache.org/jira/browse/KAFKA-12677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe updated KAFKA-12677:
---------------------------------
Priority: Major (was: Blocker)
> The raftCluster always send to the wrong active controller and never update
> ---------------------------------------------------------------------------
>
> Key: KAFKA-12677
> URL: https://issues.apache.org/jira/browse/KAFKA-12677
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 2.8.0
> Reporter: Luke Chen
> Assignee: Colin McCabe
> Priority: Major
>
> We introduce KIP-500 to introduce a Self-Managed Metadata Quorum. We should
> always have 1 active controller, and all the RPC will send to the active
> controller. But there's chances that the active controller already changed,
> but the RPC still send to the old one.
> In the attachment log, we can see:
> {code:java}
> [Controller 3002] Becoming active at controller epoch 1.
> ...
> [Controller 3000] Becoming active at controller epoch 2.
> {code}
> So, the latest active controller should be 3000. But the create topic RPC are
> all sending to controller 3002:
> {code:java}
> "errorMessage":"The active controller appears to be node 3000"
> {code}
> This bug causes the RaftClusterTests flaky.
>
> Debug log while running testCreateClusterAndCreateListDeleteTopic test:
> https://drive.google.com/file/d/1WVUgy1Erjx8mHyofiP9MVvQGb0LcDYt3/view?usp=sharing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
