You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2024/11/04 18:20:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Kirk True updated KAFKA-17732:
------------------------------
    Summary: System test coverage for new consumer positions getting behind committed offsets  (was: System test coverage for new consumer positions not getting behind committed offsets)

> 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
>            Priority: Major
>              Labels: consumer-threading-refactor
>             Fix For: 4.0.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)