You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/15 22:10:00 UTC
[jira] [Commented] (KAFKA-7296) Producer should handle
COORDINATOR_LOADING error in TxnOffsetCommit
[ https://issues.apache.org/jira/browse/KAFKA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581680#comment-16581680 ]
ASF GitHub Bot commented on KAFKA-7296:
---------------------------------------
hachikuji opened a new pull request #5514: KAFKA-7296; Handle coordinator loading error in TxnOffsetCommit
URL: https://github.com/apache/kafka/pull/5514
We should check TxnOffsetCommit responses for the COORDINATOR_LOADING_IN_PROGRESS error code and retry if we see it. Additionally, if we encounter an abortable error, we need to ensure that pending transaction offset commits are 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 GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Producer should handle COORDINATOR_LOADING error in TxnOffsetCommit
> -------------------------------------------------------------------
>
> Key: KAFKA-7296
> URL: https://issues.apache.org/jira/browse/KAFKA-7296
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
> Fix For: 2.0.1
>
>
> The producer should check for the COORDINATOR_LOADING error when handling the TxnOffsetCommit response. We fixed the logic in GroupCoordinator to correctly check for offset loading in https://github.com/apache/kafka/pull/4788. Prior to this fix, it was not possible to see this error, so we were able to get away with not having the check.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)