You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "TaiJuWu (Jira)" <ji...@apache.org> on 2025/02/18 05:10:00 UTC

[jira] [Commented] (KAFKA-17732) System test coverage for new consumer positions getting behind committed offsets

    [ https://issues.apache.org/jira/browse/KAFKA-17732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927911#comment-17927911 ] 

TaiJuWu commented on KAFKA-17732:
---------------------------------

Hi [~lianetm] , I have some questions about this issue.

1. According description from https://issues.apache.org/jira/browse/KAFKA-17674, this test could be covered by integration test, why we need to add system test for it?

2. If I can write a test for it, it should be flaky, right?

3. I am not sure what it mean `get behind the committed offsets`
The case is if the partition committed offset in consumer is 10 but the position return from broker is 9 (I think this is incorrect behavior) or 11?

Thanks for your answer!

> System test coverage for new consumer positions getting behind committed offsets
> --------------------------------------------------------------------------------
>
>                 Key: KAFKA-17732
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17732
>             Project: Kafka
>          Issue Type: Task
>          Components: clients, consumer, system tests
>            Reporter: Lianet Magrans
>            Assignee: TaiJuWu
>            Priority: Minor
>              Labels: consumer-threading-refactor
>             Fix For: 4.1.0
>
>
> We recently catch a bug where the new consumer positions would get behind the committed offsets (fixed with https://issues.apache.org/jira/browse/KAFKA-17674). It was only discovered while adding  a new system test (test_consumer_rolling_migration, not yet in trunk, PR should be available soon in trunk under https://issues.apache.org/jira/browse/KAFKA-17272)
> We should check why this failure wasn't catch with existing tests, and add a test for it (test to ensure positions are updated properly, that would fail without KAFKA-17674 and pass with it). 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)