Github user MattWhelan commented on the pull request:

    https://github.com/apache/spark/pull/4166#issuecomment-71115860
  
    BTW, I spent a few minutes pondering the deadlock scenario, and the 
delegation changes you see here.  I'm pretty sure we're safe with 1.6-style 
coarse locking, because no class from a parent classloader will ever be able to 
refer to any of the child classloader's classes (statically - instances don't 
really matter).  We don't have funky cyclic references between CLs, so I don't 
think we can have funky deadlocks.


---
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]

Reply via email to