Github user ilganeli commented on the pull request:
https://github.com/apache/spark/pull/5501#issuecomment-92986595
@rxin Does it really make sense to have this be an ```AtomicReference``` if
access to ```activeContext``` is already protected by the
```SPARK_CONTEXT_CONSTRUCTOR_LOCK``` lock? Moreover, even if
```activeContext``` becomes an ```AtomicReference```, I don't think we can
remove the existing constructor lock since creating a ```SparkContext``` will
call the constructor. Thus, I don't necessarily see an advantage to making this
an AtomicReference - please let me know if you disagree.
---
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]
