[ https://issues.apache.org/jira/browse/KAFKA-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498387#comment-17498387 ]
Luke Chen edited comment on KAFKA-13514 at 2/26/22, 3:38 AM: ------------------------------------------------------------- [~ableegoldman] , I agree with you that if this actually result in the two consumers taking ownership of the same partition at the same time, that would be a severe bug, and we should fix it soon! I have this assumption is because log output in this Jira ticket's description. However, I also saw this failed test in jenkins after this ticket opened, but no similar error logs as this ticket showed. It's just slow. I'm stilling waiting to see a failed case and check the complete logs where there is assignment error. > I'm pretty sure we haven't touched the general assignment algorithm Right, we didn't touch or change the general assignment algorithm. So this bug is already there when first written. Do you have the failed test jenkins link for me to check the complete log? Thank you. was (Author: showuon): [~ableegoldman] , I agree with you that if this actually result in the two consumers taking ownership of the same partition at the same time, that would be a severe bug, and we should fix it soon! I have this assumption is because log output in this Jira ticket's description. However, I also saw this error after this ticket opened, and no similar error logs as this ticket showed. It's just slow. I'm stilling waiting to see a failed case and check the complete logs. > I'm pretty sure we haven't touched the general assignment algorithm Right, we didn't touch or change the general assignment algorithm. So this bug is already there when first written. Do you have the failed test jenkins link for me to check the complete log? Thank you. > Flakey test StickyAssignorTest > ------------------------------ > > Key: KAFKA-13514 > URL: https://issues.apache.org/jira/browse/KAFKA-13514 > Project: Kafka > Issue Type: Test > Components: clients, unit tests > Reporter: Matthias J. Sax > Assignee: Luke Chen > Priority: Critical > Labels: flaky-test > > org.apache.kafka.clients.consumer.StickyAssignorTest.testLargeAssignmentAndGroupWithNonEqualSubscription() > No real stack trace, but only: > {quote}java.util.concurrent.TimeoutException: > testLargeAssignmentAndGroupWithNonEqualSubscription() timed out after 60 > seconds{quote} > STDOUT > {quote}[2021-12-07 01:32:23,920] ERROR Found multiple consumers consumer1 and > consumer2 claiming the same TopicPartition topic-0 in the same generation -1, > this will be invalidated and removed from their previous assignment. > (org.apache.kafka.clients.consumer.internals.AbstractStickyAssignor:150) > [2021-12-07 01:32:58,964] ERROR Found multiple consumers consumer1 and > consumer2 claiming the same TopicPartition topic-0 in the same generation -1, > this will be invalidated and removed from their previous assignment. > (org.apache.kafka.clients.consumer.internals.AbstractStickyAssignor:150) > [2021-12-07 01:32:58,976] ERROR Found multiple consumers consumer1 and > consumer2 claiming the same TopicPartition topic-0 in the same generation -1, > this will be invalidated and removed from their previous assignment. > (org.apache.kafka.clients.consumer.internals.AbstractStickyAssignor:150){quote} -- This message was sent by Atlassian Jira (v8.20.1#820001)