[
https://issues.apache.org/jira/browse/KAFKA-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458625#comment-16458625
]
ASF GitHub Bot commented on KAFKA-6829:
---------------------------------------
bbejeck opened a new pull request #4948: KAFKA-6829: Retry commits on unknown
topic or partition
URL: https://github.com/apache/kafka/pull/4948
For the UNKNOWN_TOPIC_OR_PARTITION error, we could change the consumer's
behavior to retry after this error. While this is a rare case since the user
would not commit offsets for topics unless they had been able to fetch from
them, but this doesn't really handle the situation where the broker hasn't
received any metadata updates.
Updated unit tests
### 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:
us...@infra.apache.org
> Consumer should retry when encountering unknown topic or partition error
> ------------------------------------------------------------------------
>
> Key: KAFKA-6829
> URL: https://issues.apache.org/jira/browse/KAFKA-6829
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Reporter: Bill Bejeck
> Assignee: Bill Bejeck
> Priority: Minor
>
> For the UNKNOWN_TOPIC_OR_PARTITION error, we could change the consumer's
> behavior to retry after this error. While this is a rare case since the user
> would not commit offsets for topics unless they had been able to fetch from
> them, but this doesn't really handle the situation where the broker hasn't
> received _any_ metadata updates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
