Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/5343#issuecomment-89337784
I'm somewhat dubious about whether this is needed. It takes a single
command to kill a job with yarn application -kill. Also, the advantage of the
latter is that it should return a non-zero exit code if something goes wrong,
but there's no automated way to know that a kill went through when the client
is killed. Also, for comparison, there's no similar option for killing a
MapReduce job.
---
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]
