Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2577#issuecomment-57185274
also note this does change everything to allow yarn to retry. previously
when it hit the maximum number of executor failures it didn't retry the AM. I
waffled back and forth on this one. At first the thought was that if that many
executors are dying its probably an issue with the user code, but then again if
you have a really long running job then I can think of situations you want it
to retry. Anyone have strong opinion on that?
---
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
