[
https://issues.apache.org/jira/browse/KAFKA-17732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911532#comment-17911532
]
Lianet Magrans commented on KAFKA-17732:
----------------------------------------
Hey [~taijuwu] , I just removed 4.0 as target version for this minor one given
how close we are to the deadline (we do have coverage for this issue with the
test that surfaced it, the intention is to have one specifically for it so that
it's easy to identify). So let's keep it in the radar targeting 4.1, makes
sense? Thanks!
> 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)
