[KAFKA-16623] KafkaAsyncConsumer system tests warn about revoking partitions that weren't previously assigned

• Type: Bug
• Status: In Progress
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 3.8.0
• Fix Version/s: 3.8.0
• Component/s: clients, consumer, system tests
• Labels: consumer-threading-refactor kip-848-client-support system-tests
• Assignee: Kirk True
• Reporter: Kirk True
• Created: 25/Apr/24 17:04
• Updated: 1 week ago 20:37

Description

When running system tests for the KafkaAsyncConsumer, we occasionally see this warning:

  File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.7/threading.py", line 865, in run
    self._target(*self._args, **self._kwargs)
  File "/home/jenkins/workspace/system-test-kafka-branch-builder/kafka/venv/lib/python3.7/site-packages/ducktape/services/background_thread.py", line 38, in _protected_worker
    self._worker(idx, node)
  File "/home/jenkins/workspace/system-test-kafka-branch-builder/kafka/tests/kafkatest/services/verifiable_consumer.py", line 304, in _worker
    handler.handle_partitions_revoked(event, node, self.logger)
  File "/home/jenkins/workspace/system-test-kafka-branch-builder/kafka/tests/kafkatest/services/verifiable_consumer.py", line 163, in handle_partitions_revoked
    (tp, node.account.hostname)
AssertionError: Topic partition TopicPartition(topic='test_topic', partition=0) cannot be revoked from worker20 as it was not previously assigned to that consumer

In test_fencing_static_consumer, there are two sets of consumers that use group instance IDs: the initial set and the "conflict" set. It appears that one of the "conflicting" consumers hijacks the partition ownership from the coordinator's perspective when the initial consumer leaves the group.