MINOR: add support for kafka 2.4 and 2.5 to downgrade test#8518
MINOR: add support for kafka 2.4 and 2.5 to downgrade test#8518lbradstreet wants to merge 2 commits into
Conversation
|
ok to test |
|
Result after running in ducker: |
| version=kafka_version) | ||
| self.producer.start() | ||
|
|
||
| static_membership = kafka_version == DEV_BRANCH or kafka_version >= LATEST_2_3 |
There was a problem hiding this comment.
Why does static membership make a difference here?
There was a problem hiding this comment.
Good question, without it the verifiable consumer fails with:
usage: verifiable-consumer [-h]
--broker-list HOST1:PORT1[,HOST2:PORT2[...]]
--topic TOPIC --group-id GROUP_ID
--group-instance-id GROUP_INSTANCE_ID
[--max-messages MAX-MESSAGES]
[--session-timeout TIMEOUT_MS] [--verbose]
[--enable-autocommit]
[--reset-policy RESETPOLICY]
[--assignment-strategy ASSIGNMENTSTRATEGY]
[--consumer.config CONFIG_FILE]
verifiable-consumer: error: argument --group-instance-id is required
I assumed that this check was added for a reason, however maybe it's being to strict or buggy?
There was a problem hiding this comment.
I believe it's due to 2.4 accidentally requiring --group-instance-id and in this test we end up using this version. See 0f995ba
There was a problem hiding this comment.
I could force static throttling to be used when the version is 2.4 or 2.3 and leave a comment if that works for you.
There was a problem hiding this comment.
@abbccdda I changed the code to add a static_membership parameter to the test matrix. We simply avoid this for 2.4 where this is broken due to the command line validation in that release.
|
ok to test |
|
No failures, nice :) |
The downgrade test does not currently support 2.4 and 2.5. When you enable them, it fails as a result of consumer group static membership. This PR makes the downgrade test work with all of our released versions again.