Github user o-mdr commented on the pull request:
https://github.com/apache/spark/pull/4871#issuecomment-76942656
def stop() {
SparkContext.SPARK_CONTEXT_CONSTRUCTOR_LOCK.synchronized {
This line should have prevented 2 threads from going into the inner `{...}`
and thefore changing the order of the lines wouldn't help.
@srowen if this is read by non-syncronised methods, only one of them will
be able to go inside this method and all the others will wait, correct? Thus it
could be the problem with the others methods, that run some non-synchronised
logic *before* calling into this syncronised method.
@andrewor14 Having a test would help.
---
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]