[
https://issues.apache.org/jira/browse/KAFKA-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837826#comment-17837826
]
Lianet Magrans edited comment on KAFKA-16566 at 4/16/24 6:59 PM:
-----------------------------------------------------------------
Hey [~ableegoldman], this is specific to the static membership, and related to
the consumer system tests only, that were parametrized to run with the legacy
and new protocol/consumer. You're on the right page regarding the rest: Streams
tests haven't been migrated yet because it's not integrated with the new
protocol.
Classic protocol refers to the existing group protocol, and Consumer protocol
refers to the new one introduced with KIP-848 (just using the names proposed to
be used in the configs to switch between both)
was (Author: JIRAUSER300183):
Hey [~ableegoldman], this is specific to the static membership, and related to
the consumer system tests only, that were parametrized to run with the legacy
and new coordinator/consumer. You're on the right page regarding the rest:
Streams tests haven't been migrated yet because it's not integrated with the
new protocol.
Classic protocol refers to the existing group protocol, and Consumer protocol
refers to the new one introduced with KIP-848 (just using the names proposed to
be used in the configs to switch between both)
> Update consumer static membership fencing system test to support new protocol
> -----------------------------------------------------------------------------
>
> Key: KAFKA-16566
> URL: https://issues.apache.org/jira/browse/KAFKA-16566
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 3.7.0
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Major
> Labels: kip-848-client-support
> Fix For: 3.8.0
>
>
> consumer_test.py contains OffsetValidationTest.test_fencing_static_consumer
> that verifies the sequence in which static members join a group when using
> conflicting instance id. This behaviour is different in the classic and
> consumer protocol, so the tests should be updated to set the right
> expectations when running with the new consumer protocol. Note that what the
> tests covers (params, setup), apply to both protocols. It is the expected
> results that are not the same.
> When conflicts between static members joining a group:
> Classic protocol: all members join the group with the same group instance id,
> and then the first one will eventually receive a HB error with
> FencedInstanceIdException
> Consumer protocol: new member with an instance Id already in use is not able
> to join, receiving an UnreleasedInstanceIdException in the response to the HB
> to join the group.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
