[STREAMING][FLAKY-TEST] Catch execution context race condition in FileBasedWriteAheadLog.close()#9953
Closed
brkyvz wants to merge 1 commit intoapache:masterfrom
Closed
[STREAMING][FLAKY-TEST] Catch execution context race condition in FileBasedWriteAheadLog.close()#9953brkyvz wants to merge 1 commit intoapache:masterfrom
FileBasedWriteAheadLog.close()#9953brkyvz wants to merge 1 commit intoapache:masterfrom
Conversation
Contributor
|
LGTM. @zsxwing what do you think? |
|
Test build #46654 has finished for PR 9953 at commit
|
Member
|
LGTM |
Member
|
Thanks! Merging to master and 1.6 |
asfgit
pushed a commit
that referenced
this pull request
Nov 25, 2015
…leBasedWriteAheadLog.close()` There is a race condition in `FileBasedWriteAheadLog.close()`, where if delete's of old log files are in progress, the write ahead log may close, and result in a `RejectedExecutionException`. This is okay, and should be handled gracefully. Example test failures: https://amplab.cs.berkeley.edu/jenkins/job/Spark-1.6-SBT/AMPLAB_JENKINS_BUILD_PROFILE=hadoop1.0,label=spark-test/95/testReport/junit/org.apache.spark.streaming.util/BatchedWriteAheadLogWithCloseFileAfterWriteSuite/BatchedWriteAheadLog___clean_old_logs/ The reason the test fails is in `afterEach`, `writeAheadLog.close` is called, and there may still be async deletes in flight. tdas zsxwing Author: Burak Yavuz <brkyvz@gmail.com> Closes #9953 from brkyvz/flaky-ss. (cherry picked from commit a5d9887) Signed-off-by: Shixiong Zhu <shixiong@databricks.com>
Member
|
@brkyvz no JIRA for this one? |
Contributor
Author
|
@zsxwing No. We could create one though if we like |
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
4 participants
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.
There is a race condition in
FileBasedWriteAheadLog.close(), where if delete's of old log files are in progress, the write ahead log may close, and result in aRejectedExecutionException. This is okay, and should be handled gracefully.Example test failures:
https://amplab.cs.berkeley.edu/jenkins/job/Spark-1.6-SBT/AMPLAB_JENKINS_BUILD_PROFILE=hadoop1.0,label=spark-test/95/testReport/junit/org.apache.spark.streaming.util/BatchedWriteAheadLogWithCloseFileAfterWriteSuite/BatchedWriteAheadLog___clean_old_logs/
The reason the test fails is in
afterEach,writeAheadLog.closeis called, and there may still be async deletes in flight.@tdas @zsxwing