-
Notifications
You must be signed in to change notification settings - Fork 40
Fix RFS Shutdown logic during exception cases and set kafka tests as isolated #1385
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
Conversation
Signed-off-by: Andre Kurait <[email protected]>
Signed-off-by: Andre Kurait <[email protected]>
Signed-off-by: Andre Kurait <[email protected]>
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.
🤞 All my comments are optional, really would like to see this get our CI unblocked.
if (successorWorkItemIds.size() == 1 && workItemId.equals(successorWorkItemIds.get(0))) { | ||
log.atWarn().setMessage("No real progress was made for work item: {}. Will retry with larger timeout").addArgument(workItemId).log(); |
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.
This is a strange case, it seems like the getSuccessorWorkItemIds
should error out internally before returning up to this level. Can we rework this?
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.
getSuccessorWorkItemIds does error out, but this should really be a warn instead of an error.
The case here is that the lease is just long enough to send one request to the target cluster successfully, getSuccessorWorkItemIds does throw.
With the new try catch, this would be caught, but this isn't an "Error" case, more of a Warn which is why we shouldn't rely on that exception in getSuccessorWorkItemIds
} else { | ||
log.atWarn().setMessage("No progress cursor to create successor work items from. This can happen when" + | ||
"downloading and unpacking shard takes longer than the lease").log(); | ||
log.atWarn().setMessage("Skipping creation of successor work item to retry the existing one with more time") | ||
.log(); | ||
} |
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.
Nit: Can we invert the flow of control and return if the precondition fails right away?
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.
Ideally we'd have only one 'level' of if/elseif/else blocks for each function, makes it much cleaner to read.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1385 +/- ##
============================
============================
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
Fix RFS Shutdown logic during exception cases
Set kafka tests as isolated
Remove deprecated usage of KafkaContainer in favor of ConfluentKafkaContainer
Issues Resolved
MIGRATIONS-2461
MIGRATIONS-2460
Testing
GHA
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.