You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Onur Karaman (JIRA)" <ji...@apache.org> on 2016/11/15 08:59:58 UTC
[jira] [Updated] (KAFKA-4410) KafkaController sends double the
expected number of StopReplicaRequests during controlled shutdown
[ https://issues.apache.org/jira/browse/KAFKA-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Onur Karaman updated KAFKA-4410:
--------------------------------
Description:
We expect KafkaController to send the broker undergoing controlled shutdown one StopReplicaRequest for each follower replica on that broker. Examining KafkaController.shutdownBroker, we see that this is not the case:
1. KafkaController.shutdownBroker itself sends the shutting down broker a StopReplicaRequest for each follower replica
2. KafkaController.shutdownBroker transitions every follower replica to OfflineReplica in its call to replicaStateMachine.handleStateChanges, which also sends the shutting down broker a StopReplicaRequest.
was:
We expect KafkaController to send one StopReplicaRequest for each follower replica on the broker undergoing controlled shutdown. Examining KafkaController.shutdownBroker, we see that this is not the case:
1. KafkaController.shutdownBroker itself sends a StopReplicaRequest for each follower replica
2. KafkaController.shutdownBroker transitions every follower replica to OfflineReplica in its call to replicaStateMachine.handleStateChanges, which also sends a StopReplicaRequest.
> KafkaController sends double the expected number of StopReplicaRequests during controlled shutdown
> --------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4410
> URL: https://issues.apache.org/jira/browse/KAFKA-4410
> Project: Kafka
> Issue Type: Bug
> Reporter: Onur Karaman
> Assignee: Onur Karaman
>
> We expect KafkaController to send the broker undergoing controlled shutdown one StopReplicaRequest for each follower replica on that broker. Examining KafkaController.shutdownBroker, we see that this is not the case:
> 1. KafkaController.shutdownBroker itself sends the shutting down broker a StopReplicaRequest for each follower replica
> 2. KafkaController.shutdownBroker transitions every follower replica to OfflineReplica in its call to replicaStateMachine.handleStateChanges, which also sends the shutting down broker a StopReplicaRequest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)