Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-192736752
Spotted the problem: we need an extra `releaseLock()` call in
`getOrElseUpdate`'s "block already exists" branch; see 9dc510c. I can spin this
change off into a smaller patch against master in case we want to clean up the
log noise sooner.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
