Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2683#issuecomment-58269418
Due to the `CONFIGURATION_INSTANTIATION_LOCK` thread-safety issue, I think
that we'll still end up having to serialize the Configuration separately. If
we didn't, then we'd have to hold `CONFIGURATION_INSTANTIATION_LOCK` while
deserializing each task, which could have a huge performance penalty (it's fine
to hold the lock while loading the Configuration, since that doesn't take too
long).
Therefore, I don't think that we'll be able to safely remove this
complexity, so I'm going to recommend closing this PR in favor of applying the
small #2684 fix in 1.2.
---
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]
