You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:04:25 UTC
[jira] [Updated] (SPARK-21821) Support to force kill the
CoarseGrainedExecutorBackend process which is likely be orphaned.
[ https://issues.apache.org/jira/browse/SPARK-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-21821:
---------------------------------
Labels: bulk-closed (was: )
> Support to force kill the CoarseGrainedExecutorBackend process which is likely be orphaned.
> -------------------------------------------------------------------------------------------
>
> Key: SPARK-21821
> URL: https://issues.apache.org/jira/browse/SPARK-21821
> Project: Spark
> Issue Type: New Feature
> Components: Spark Core
> Affects Versions: 2.2.0
> Reporter: zuotingbing
> Priority: Major
> Labels: bulk-closed
>
> In out production environments, it often happens that even the application has finished, but the CoarseGrainedExecutorBackend process still exists and take up the resource.
> Take a look at ExecutorRunner.scala, it maybe failed to terminate process in killProcess method for some reason. In this case, the process of CoarseGrainedExecutorBackend will likely be orphaned. It would be great to support a script to kill the CoarseGrainedExecutorBackend process forcibly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org