[
https://issues.apache.org/jira/browse/KAFKA-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857046#comment-16857046
]
ASF GitHub Bot commented on KAFKA-8386:
---------------------------------------
hachikuji commented on pull request #6762: KAFKA-8386: Use
COORDINATOR_NOT_AVAILABLE to replace UNKNOWN_MEMBER_ID exception when group is
dead or not found
URL: https://github.com/apache/kafka/pull/6762
----------------------------------------------------------------
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
> Use COORDINATOR_NOT_AVAILABLE to replace UNKNOWN_MEMBER_ID when the group is
> not available
> ------------------------------------------------------------------------------------------
>
> Key: KAFKA-8386
> URL: https://issues.apache.org/jira/browse/KAFKA-8386
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Boyang Chen
> Assignee: Boyang Chen
> Priority: Major
>
> When the group is dead or unavailable on the coordinator, current approach is
> to return `UNKNOWN_MEMBER_ID` to let the member reset generation and rejoin.
> It is not particularly safe for static members in this case, since resetting
> `member.id` could delay the detection for duplicate instance.id.
> Also considering the fact that group unavailability could mostly be caused by
> migration, it is favorable to trigger a coordinator rediscovery immediately
> than one more bounce. Thus, we decide to use `COORDINATOR_NOT_AVAILABLE` as
> top line citizen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
