[jira] [Commented] (KAFKA-14419) Failed SyncGroup leading to partitions lost due to processing during rebalances

[ https://issues.apache.org/jira/browse/KAFKA-14419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783924#comment-17783924 ] Mikael commented on KAFKA-14419: [~mjsax] The reduced session.timeout.ms is because we w

[jira] [Commented] (KAFKA-14419) Failed SyncGroup leading to partitions lost due to processing during rebalances

[ https://issues.apache.org/jira/browse/KAFKA-14419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782018#comment-17782018 ] Mikael commented on KAFKA-14419: In our use case there is no long processing latency. Al

[jira] [Commented] (KAFKA-14419) Same message consumed again by the same stream task after partition is lost and reassigned

[ https://issues.apache.org/jira/browse/KAFKA-14419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780038#comment-17780038 ] Mikael commented on KAFKA-14419: Hi Sophie, and thanks for the suggested workaround. We

[jira] [Comment Edited] (KAFKA-14419) Same message consumed again by the same stream task after partition is lost and reassigned

[ https://issues.apache.org/jira/browse/KAFKA-14419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680544#comment-17680544 ] Mikael edited comment on KAFKA-14419 at 1/25/23 10:35 AM: -- Hi,

[jira] [Commented] (KAFKA-14419) Same message consumed again by the same stream task after partition is lost and reassigned

[ https://issues.apache.org/jira/browse/KAFKA-14419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680544#comment-17680544 ] Mikael commented on KAFKA-14419: Hi, sorry about the log delay. Now I finally got around

[jira] [Commented] (KAFKA-14419) Same message consumed again by the same stream task after partition is lost and reassigned

[ https://issues.apache.org/jira/browse/KAFKA-14419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647556#comment-17647556 ] Mikael commented on KAFKA-14419: Still seeing consumer duplication (this is when stoppin

[jira] [Commented] (KAFKA-14419) Same message consumed again by the same stream task after partition is lost and reassigned

[ https://issues.apache.org/jira/browse/KAFKA-14419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646033#comment-17646033 ] Mikael commented on KAFKA-14419: Thanks, I'll try that out. I did see the same symptom b

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645580#comment-17645580 ] Mikael commented on KAFKA-14362: The spring-kafka defect is fixed in spring-kafka 3.0.1

[jira] [Updated] (KAFKA-14419) Same message consumed again by the same stream task after partition is lost and reassigned

[ https://issues.apache.org/jira/browse/KAFKA-14419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael updated KAFKA-14419: --- Description: Trigger scenario: Four Kafka client application instances on separate EC2 instances with a tot

[jira] [Updated] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael updated KAFKA-14362: --- Attachment: (was: KAFKA-14362_Do_not_return_any_records_from_KafkaConsumer_poll()_while_rebalance_is_in_

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638282#comment-17638282 ] Mikael commented on KAFKA-14362: Created KAFKA-14419 for the stream consumer duplication

[jira] [Created] (KAFKA-14419) Same message consumed again by the same stream task after partition is lost and reassigned

Mikael created KAFKA-14419: -- Summary: Same message consumed again by the same stream task after partition is lost and reassigned Key: KAFKA-14419 URL: https://issues.apache.org/jira/browse/KAFKA-14419 Projec

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638225#comment-17638225 ] Mikael commented on KAFKA-14362: I can confirm that there is no duplication in this scen

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637682#comment-17637682 ] Mikael commented on KAFKA-14362: Hang on, I just spotted something in spring-kafka: fail

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637614#comment-17637614 ] Mikael commented on KAFKA-14362: This patch in kafka-clients fixed the duplication issue

[jira] [Updated] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael updated KAFKA-14362: --- Attachment: KAFKA-14362_Do_not_return_any_records_from_KafkaConsumer_poll()_while_rebalance_is_in_prog.patch

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636769#comment-17636769 ] Mikael commented on KAFKA-14362: I think I have identified the root cause of the duplica

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636182#comment-17636182 ] Mikael commented on KAFKA-14362: Workaround didn't help. It seems that the first failing

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635921#comment-17635921 ] Mikael commented on KAFKA-14362: No, no errors or warnings related to rebalancing. I'm c

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635370#comment-17635370 ] Mikael commented on KAFKA-14362: When comparing successful test runs with those that gen

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633763#comment-17633763 ] Mikael commented on KAFKA-14362: We are using KafkaMessageListenerContainer from spring-

[jira] [Updated] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael updated KAFKA-14362: --- Description: Trigger scenario: Two Kafka client application instances on separate EC2 instances with one c

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631265#comment-17631265 ] Mikael commented on KAFKA-14362: I would have thought that an orderly rebalance wouldn't

[jira] [Updated] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael updated KAFKA-14362: --- Description: Trigger scenario: Two Kafka client application instances on separate EC2 instances with one c

[jira] [Commented] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

[ https://issues.apache.org/jira/browse/KAFKA-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629832#comment-17629832 ] Mikael commented on KAFKA-14362: The main thing that has caught my attention is the tigh

[jira] [Created] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

Mikael created KAFKA-14362: -- Summary: Same message consumed by two consumers in the same group after client restart Key: KAFKA-14362 URL: https://issues.apache.org/jira/browse/KAFKA-14362 Project: Kafka