Page History

...

1. For static member, `group.instance.id` must be provided. Client could optionally provide a `member.id` when `group.instance.id` is configured non-empty. If `member.id` is provided, the member will only be removed if the `member.id` matches. Otherwise, only the `group.instance.id` is used. The `member.id` serves as a validation here, which currently will not be used (set to empty string) but potentially useful if we do fully automated removal process.
2. For leave group requests under dynamic membership, it will apply a singleton list of `member.id` that it is currently using, and a singleton list of `group.instance.id` which is set to empty string. If this is the case, we shall just remove the given dynamic member the same way as current leave group logic.

...

1. Error cases expected are:
   1. Some instance ids (non-empty) are not found, which means the request is not valid (GROUP_INSTANCE_ID_INVALID, defined in the public changes section)
   2. The length of MemberIdList doesn't match length of GroupInstanceIdList (MEMBER_ID_MISMATCH, defined in the public changes section)
   3. A theoretical case would be that both `member.id` and `group.instance.id` are set to empty string. We shall

...

1. 1. expose error in the server log

...

1. 1. . If the entire batch request is configured with empty strings, UNKNOWN_MEMBER_ID error

...

1. 1. will be returned.

Command Line API for Membership Management

...

1. The broker is on an old version (UNSUPPORTED_VERSION)
2. Consumer group does not exist (INVALID_GROUP_ID)
3. Operator is not authorized. (GROUP_AUTHORIZATION_FAILED)
4. Some instance ids (non-empty) are not found, which means the request is not valid (GROUP_INSTANCE_ID_INVALID, defined in the public changes section)
5. The length of MemberIdList doesn't match length of GroupInstanceIdList (MEMBER_ID_MISMATCH, defined in the public changes section)LeaveGroupRequest specific error

We need to enforce special access to these APIs for the end user who may not be in administrative role of Kafka Cluster. The solution is to allow a similar access level to the join group request, so the consumer service owner could easily use this API.

...