You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "RaidenE1 (via GitHub)" <gi...@apache.org> on 2025/07/16 19:58:58 UTC
[PR] KAFKA-19511: Fix flaky test HandlingSourceTopicDeletionIntegrationTest.shouldThrowErrorAfterSourceTopicDeleted [kafka]
RaidenE1 opened a new pull request, #20183:
URL: https://github.com/apache/kafka/pull/20183
Ticket here: https://issues.apache.org/jira/browse/KAFKA-19511
Original timeout for HandlingSourceTopicDeletionIntegrationTest is 60s which is not enough. Sometimes the state of Kafka streams thread needs around 100s to change the state from PENDING ERROR to ERROR, as it still try to poll data while the source topic is missing, also while leaving the consumer group it will reach the timeout for 30s.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] KAFKA-19511: Fix flaky test HandlingSourceTopicDeletionIntegrationTest.shouldThrowErrorAfterSourceTopicDeleted [kafka]
Posted by "mjsax (via GitHub)" <gi...@apache.org>.
mjsax commented on PR #20183:
URL: https://github.com/apache/kafka/pull/20183#issuecomment-3081653168
Thanks for the PR. I am not sure if I fully understand. I believe this issue with this test was introduced when `streams` protocol was added. But why does it modify the behavior in the way you describe?
What you describe sounds very generic and I am wondering why it was not a problem for `classic` protocol?
Btw: Looking into the test, it seems we are leaking `KafkaStreams()` instances, as we don't `close()` them. Can we extend this PR to use try-with-resource to ensure we don't leak instances?
Another minor fix could be, to replace `Serdes.Integer().getClass()` in the config setup with `Serdes.IntegerSerde.class`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] KAFKA-19511: Fix flaky test HandlingSourceTopicDeletionIntegrationTest.shouldThrowErrorAfterSourceTopicDeleted [kafka]
Posted by "RaidenE1 (via GitHub)" <gi...@apache.org>.
RaidenE1 commented on PR #20183:
URL: https://github.com/apache/kafka/pull/20183#issuecomment-3081927704
@mjsax Yeah, it only happens in the new protocol, I've run it for a hundred times maybe, old protocols are all good, have of the new test spend 100s and failed the original test since it's set to 60s.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] KAFKA-19511: Fix flaky test HandlingSourceTopicDeletionIntegrationTest.shouldThrowErrorAfterSourceTopicDeleted [kafka]
Posted by "RaidenE1 (via GitHub)" <gi...@apache.org>.
RaidenE1 closed pull request #20183: KAFKA-19511: Fix flaky test HandlingSourceTopicDeletionIntegrationTest.shouldThrowErrorAfterSourceTopicDeleted
URL: https://github.com/apache/kafka/pull/20183
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org