Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3112#issuecomment-62483559
I don't think that this problem is limited to YARN; I think that I've also
seen when submitting jobs to a standalone cluster using `spark-submit`'s
`cluster` deploy mode. If a user has set `spark.driver.host` in their default
configuration file and submits the driver to a remote machine for which this
setting is invalid, then I think they'll still run into this error.
When using a cluster deploy mode, whether through YARN or Spark's
standalone cluster manager, I think we should completely ignore any values of
`spark.driver.host` that might have been inherited from the submitting machine.
---
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]
