You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2020/05/08 17:12:31 UTC
[GitHub] [spark] holdenk commented on pull request #26440: [SPARK-20628][CORE][K8S] Start to improve Spark decommissioning & preemption support
holdenk commented on pull request #26440:
URL: https://github.com/apache/spark/pull/26440#issuecomment-625920742
I'm having difficulty understanding your concern @Ngone51
So in standalone mode it's up to the user to write their decommissioning shell script and register it with the cloud provider or whatever mechanism is being used to notify the executors of decommissioning (or if it's maintenance then send the signal manually). All of the executors will not shut down because one executor receives a SIGPWR. WorkerWatcher just checks to make sure the RPC connection stills works and we don't shut down the RPC mechanism during decommissioning.
Can you point out what in my understanding doesn't match your understanding?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org