-
Notifications
You must be signed in to change notification settings - Fork 14.5k
KAFKA-19516: Added a request timeout of 120000ms to CreateTopics in ShareFetchAcknolwedgeRequestTest methods #20184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: trunk
Are you sure you want to change the base?
Conversation
@chirag-wadhwa5 Can you pelase link the flaky test failure here, I cheked here and can see flakiness. But it's for some other reason than you mentioned. |
…rs in GroupCoordinatorBaseRequestTest after the topic creation
@@ -131,8 +132,15 @@ class GroupCoordinatorBaseRequestTest(cluster: ClusterInstance) { | |||
controllers = controllerServers(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of the timeout - could we do something like waitUntilTrue? Basically I want retries instead on one long call.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review. I have made this change, and now the call TestUtils.createTopicWithAdmin
is made inside a waitUntilTrue
msg = "Failed to create topic with admin within 2 minutes", | ||
waitTimeMs = 2 * 60 * 1000, // 2 minutes in milliseconds | ||
pause = 40 * 1000 // 40 seconds in milliseconds |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just out of curiosity, why does the CreateTopic operation sometimes take up to 2 minutes to succeed? Is there a configuration that controls this behavior?
This PR works is an aim to resolve the flakiness in the ShareFetchAcknolwedgeRequestTest tests. Recently some flakes were seen on the test and it was reproduced locally as well, with the error ->
Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. Call: createTopics
. This PR tries to resolve that by adding an increased timeout of 120000ms (2 minutes) to the CreateTopics request sent out.