You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Sönke Liebau (JIRA)" <ji...@apache.org> on 2019/07/30 08:07:00 UTC

[jira] [Resolved] (KAFKA-1099) StopReplicaRequest and StopReplicaResponse should also carry the replica ids

     [ https://issues.apache.org/jira/browse/KAFKA-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sönke Liebau resolved KAFKA-1099.
---------------------------------
    Resolution: Abandoned

Closing this as abandoned after asking for feedback on the dev list and receiving no objections.

> 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)