Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/3841#issuecomment-68760646
@WangTaoTheTonic I understand the problem you're observing and think it's
related specifically to YARN. Without being super familiar with YARN, I think
the approach this patch should take is to send the config option via a system
property with a -D flag to the executor, and immediately put that System
property into a stub SparkEnv object. When the real SparkEnv object comes over
the wire, the two can be merged (or maybe the first can be dropped). This way
we don't have to change to reading from System properties in other places, like
`Utils.maxPortRetries`
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
