[
https://issues.apache.org/jira/browse/KAFKA-14948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Proven Provenzano resolved KAFKA-14948.
---------------------------------------
Resolution: Cannot Reproduce
I updated my code to tip of master and cannot reproduce it anymore.
> Broker fails to rejoin cluster when cluster is in dual write mode
> -----------------------------------------------------------------
>
> Key: KAFKA-14948
> URL: https://issues.apache.org/jira/browse/KAFKA-14948
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Affects Versions: 3.5.0
> Reporter: Proven Provenzano
> Assignee: Proven Provenzano
> Priority: Major
>
> While testing migration dual write mode I came across this issue.
> Initial setup: A single ZK node and a single Broker. Create a topic with some
> data.
> Create a single controller and initiate migrations.
> Update Broker to start migration.
> Wait until all records are migrated. Cluster should be in dual write mode at
> this point.
> Kill and restart the broker. Sometimes the broker will not rejoin the cluster
> and consuming records from a topic will fail to find topic.
> Restarting the Controller will fix this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
