Github user tgravescs commented on the issue:

    https://github.com/apache/spark/pull/18897
  
    I think the kill is to more cleanly shutdown on the yarn side of things.  
If you yarn kill an application on yarn it doesn't set the history 
appropriately, etc.  Its also just nice to have one spot to go to do things, 
similar to mapred, pig, oozie, type commands.
    
    I think we can definitely split this up into 2 prs, one for the rpc layer 
changes (which requires some lower level changes due to authentication with 
tokens) and then one for the kill command itself, does that sounds good @vanzin?


---
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

Reply via email to