[
https://issues.apache.org/jira/browse/SPARK-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Rosen resolved SPARK-2585.
---
Resolution: Fixed
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'm closing this as Won't Fix. The thread-safety issues with
Configuration will be addressed by a separate clone() patch.
Remove special handling of Hadoop JobConf
-
Key: SPARK-2585
URL: https://issues.apache.org/jira/browse/SPARK-2585
Project: Spark
Issue Type: Improvement
Components: Spark Core
Reporter: Patrick Wendell
Assignee: Josh Rosen
Priority: Critical
This is a follow up to SPARK-2521 and should close SPARK-2546 (provided the
implementation does not use shared conf objects). We no longer need to
specially broadcast the Hadoop configuration since we are broadcasting RDD
data anyways.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
