[
https://issues.apache.org/jira/browse/KAFKA-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015536#comment-17015536
]
ASF GitHub Bot commented on KAFKA-9235:
---------------------------------------
hachikuji commented on pull request #7963: KAFKA-9235; Ensure transaction
coordinator is stopped after replica deletion
URL: https://github.com/apache/kafka/pull/7963
During a reassignment, it can happen that the current leader of a partition
is demoted and removed from the replica set at the same time. In this case, we
rely on the StopReplica request in order to stop replica fetchers and to clear
the group coordinator cache. This patch adds similar logic to ensure that the
transaction coordinator state cache also gets cleared.
### 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:
us...@infra.apache.org
> 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
>
> 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)
