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

Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/01/16 22:53:00 UTC

[jira] [Resolved] (KAFKA-9235) Transaction state not cleaned up following StopReplica request

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

Jason Gustafson resolved KAFKA-9235.
------------------------------------
    Fix Version/s: 2.4.1
       Resolution: Fixed

> Transaction state not cleaned up following StopReplica request
> --------------------------------------------------------------
>
>                 Key: KAFKA-9235
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9235
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>             Fix For: 2.4.1
>
>
> When the broker receives a StopReplica request from the controller for one of the transaction state topics, we should make sure to cleanup existing state in the TransactionCoordinator for the corresponding partition. We have similar logic already for the group coordinator.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)