GitHub user jiangxb1987 opened a pull request:
https://github.com/apache/spark/pull/18076
[SPARK-18406][CORE] Race between end-of-task and completion iterator read
lock release
## What changes were proposed in this pull request?
When a TaskContext is not propagated properly to all child threads for the
task, just like the reported cases in this issue, we fail to get to TID from
TaskContext and that causes unable to release the lock and assertion failures.
To resolve this, we have to explicitly pass the TID value to the `unlock`
method.
## How was this patch tested?
Add new failing regression test case in `RDDSuite`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jiangxb1987/spark completion-iterator
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/18076.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #18076
----
commit 740dc1923d75f3980ad3e815d36af0685fe2aaef
Author: Xingbo Jiang <[email protected]>
Date: 2017-05-23T23:16:57Z
bugfix
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
