-
Notifications
You must be signed in to change notification settings - Fork 14.5k
KAFKA-19422: Deflake streams_application_upgrade_test #20004
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
In this upgrade test, applications sometimes crash before the upgrade, so it's actually triggering a bug in several older versions (2.x and possibly others). It seems to be a rare race condition that has been happening since 2022. Since we are not going to roll out a patch release for Kafka Streams 2.x, we should just allow applications to crash before the upgrade.
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.
Pull Request Overview
This PR updates the upgrade test for Kafka Streams to allow for applications crashing on shutdown in older versions. The changes modify verification patterns to accept either "EXCEPTION" or "CLOSED" events rather than only "CLOSED", thereby deflaking the streams application upgrade test.
- Updated wait_for_verification regex patterns in the test for processor nodes.
- Adjusted SSH grep commands to match the new regex pattern.
PTAL @aliehsaeedii |
self.wait_for_verification(self.processor2, "SMOKE-TEST-CLIENT-CLOSED", self.processor2.STDOUT_FILE) | ||
self.wait_for_verification(self.processor3, "SMOKE-TEST-CLIENT-CLOSED", self.processor3.STDOUT_FILE) | ||
# some older versions crash on shutdown, so we allow crashes here. | ||
self.wait_for_verification(self.processor1, "SMOKE-TEST-CLIENT-(EXCEPTION|CLOSED)", self.processor1.STDOUT_FILE) |
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.
Should we add a version check, and apply this new verification only for the older version(s) which are problematic?
Same below.
In this upgrade test, applications sometimes crash before the upgrade,
so it's actually triggering a bug in several older versions (2.x and
possibly others). It seems to be a rare race condition that has been
happening since 2022. Since we are not going to roll out a patch release
for Kafka Streams 2.x, we should just allow applications to crash before
the upgrade.