[
https://issues.apache.org/jira/browse/KAFKA-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837820#comment-17837820
]
A. Sophie Blee-Goldman commented on KAFKA-16566:
------------------------------------------------
I'm a bit confused – I thought we haven't migrated Streams over to the new
consumer rebalancing protocol. Or is this referring to something else? What is
the "classic" vs "consumer" protocol? And when/why did we migrate our system
tests to using it? Does it have to do with static membership specifically?
Sorry for being out of the loop here
> Update 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)
