Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2684#issuecomment-59578207
@frydawg524 Thanks for testing this out! I'm glad to hear that it solves
the bug.
I just pushed a new commit which adds a configuration option
(`spark.hadoop.cloneConf`) for controlling whether to clone the configuration
(as in the patch you tested) or share a single configuration object across all
tasks (the old code). The reasoning for this is that releasing 1.1.1 and 1.0.3
patches that cause measurable performance regressions will upset users who
weren't affected by this issue. In 1.2, we may revisit this by seeing if we
can find ways to make the cloning process faster.
I also plan to open an upstream ticket with Hadoop. That won't solve the
problem for Spark users who might be stuck using older Hadoop versions (so we
still need our own workaround), but it would be nice to see this eventually get
fixed upstream.
---
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]
