HDDS-6661. TestBackgroundPipelineScrubber.testRun() fails intermittently#3359
Merged
Conversation
guihecheng
approved these changes
Apr 28, 2022
| private final long intervalInMillis; | ||
| private final long waitTimeInMillis; | ||
| private long lastTimeToBeReadyInMillis = 0; | ||
| private volatile boolean runImmediately = false; |
Contributor
There was a problem hiding this comment.
Oh, it is a nice trick, so now the UT covers both the running and wait state of the scrubber thread.
Thanks a lot, LGTM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
I believe the reason is that when the
notifyStatusChanged()method is called, the thread may be running and not waiting.Then calling notifyAll() does not do anything. The thread will fall into the wait and stay stuck there until the wait interval expires, or another notify() call is received.
I think the test can be made to run reliably by using a volatile boolean to skip the wait along with the notify.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6661
How was this patch tested?
Modified unit test