Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/539#issuecomment-41351097
Personal opinion: the less cluster-specific options we have the better, so
unless there's a very compelling reason to keep SPARK_YARN_APP_NAME supported,
I'd just remove it and use the configured app name always. It seems to me, from
the code, that it was just a workaround for the real bug anyway (the app name
not being read from the config, but from the JVM system properties).
---
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.
---
