[
https://issues.apache.org/jira/browse/KAFKA-16460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897211#comment-17897211
]
PoAn Yang edited comment on KAFKA-16460 at 11/12/24 11:33 AM:
--------------------------------------------------------------
Hi [~kirktrue], I also can reproduce the same case in my cluster.
-IIUC, the consumer A's assignment is revoked, because the node receive
SIGTERM. After that, another consumer (B) will starts and keep polling.- The
question is that: why consumer B doesn't start from consumer A's last offset?
The consumer B still starts from offset 0.
was (Author: JIRAUSER300229):
Hi [~kirktrue], I also can reproduce the same case in my cluster.
IIUC, the consumer A's assignment is revoked, because the node receive SIGTERM.
After that, another consumer (B) will starts and keep polling. The question is
that: why consumer B doesn't start from consumer A's last offset? The consumer
B still starts from offset 0.
> New consumer times out consuming records in multiple consumer_test.py system
> tests
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-16460
> URL: https://issues.apache.org/jira/browse/KAFKA-16460
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer, system tests
> Affects Versions: 3.7.0
> Reporter: Kirk True
> Assignee: PoAn Yang
> Priority: Critical
> Labels: kip-848-client-support, system-tests
> Fix For: 4.0.0
>
> Attachments: verifiable_consumer_worker_A.log,
> verifiable_consumer_worker_A.stdout, verifiable_consumer_worker_B.log,
> verifiable_consumer_worker_B.stdout
>
>
> The {{consumer_test.py}} system test fails with the following errors:
> {quote}
> * Timed out waiting for consumption
> {quote}
> Affected tests:
> * {{test_broker_failure}}
> * {{test_consumer_bounce}}
> * {{test_static_consumer_bounce}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)