Github user piaozhexiu commented on the pull request:

    https://github.com/apache/spark/pull/5343#issuecomment-90205393
  
    I see. Thanks for the clarification.
    
    That's a valid point. You're right that I can't 100% guarantee whether the 
kill was executed or not. But as long as job flows are designed to be 
idempotent, that shouldn't really matter. Production jobs that run in cloud 
like ours follow the best practice anyway.
    
    The main motivation for me to add this option was to free up cluster 
resources as much as possible on a best-effort basis.


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

Reply via email to