[
https://issues.apache.org/jira/browse/KAFKA-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888786#comment-16888786
]
Sönke Liebau commented on KAFKA-1099:
-------------------------------------
Pretty sure this information has not been included in the requests until now
(at least I cannot find it in the code), but as this is now 6 years old, is
this still relevant or has become obsolete by different changes in the meantime?
> StopReplicaRequest and StopReplicaResponse should also carry the replica ids
> ----------------------------------------------------------------------------
>
> Key: KAFKA-1099
> URL: https://issues.apache.org/jira/browse/KAFKA-1099
> Project: Kafka
> Issue Type: Bug
> Components: controller
> Affects Versions: 0.8.1
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Priority: Major
>
> The stop replica request and response only contain a list of partitions for
> which a replica should be moved to offline/nonexistent state. But the replica
> id information is implicit in the network layer as the receiving broker. This
> complicates stop replica response handling on the controller. This blocks the
> right fix for KAFKA-1097 since it requires invoking callback for processing a
> StopReplicaResponse and it requires to know the replica id from the
> StopReplicaResponse.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
