You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Boyang Chen (JIRA)" <ji...@apache.org> on 2019/05/17 22:44:00 UTC
[jira] [Created] (KAFKA-8386) Use COORDINATOR_NOT_AVAILABLE to
replace UNKNOWN_MEMBER_ID when the group is not available
Boyang Chen created KAFKA-8386:
----------------------------------
Summary: 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
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)