[
https://issues.apache.org/jira/browse/KAFKA-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817217#comment-16817217
]
ASF GitHub Bot commented on KAFKA-8152:
---------------------------------------
hachikuji commented on pull request #6580: KAFKA-8152; Controller should
transition offline replicas on startup
URL: https://github.com/apache/kafka/pull/6580
When the controller starts up, we need to transition both online and offline
replicas so that even offline state will be propagated to other brokers in the
cluster. This patch also moves `ControllerChannelManager` out of
`ControllerContext` since it was not really used there.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Offline partition state not propagated by controller
> ----------------------------------------------------
>
> Key: KAFKA-8152
> URL: https://issues.apache.org/jira/browse/KAFKA-8152
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> Currently when the controller starts up, only the state of online partitions
> will be sent to other brokers. Any broker which is started or restarted after
> the controller will see only a subset of the partitions of any topic which
> has offline partitions. If all the partitions for a topic are offline, then
> the broker will not know of the topic at all. As far as I can tell, the bug
> is the fact that `ReplicaStateMachine.startup` only does an initial state
> change for replicas which are online.
> This can be reproduced with the following steps:
> # Startup two brokers
> # Create a single partition topic with rf=1
> # Shutdown the broker where the replica landed
> # Shutdown the other broker
> # Restart the broker without the replica
> # Run `kafka-topics --describe --bootstrap-server \{server ip}`
> Note that the metadata inconsistency will only be apparent when using
> `bootstrap-server` in `kafka-topics.sh`. Using zookeeper, everything will
> seem normal.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
