You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "He Tianyi (JIRA)" <ji...@apache.org> on 2016/05/16 03:00:27 UTC

[jira] [Created] (SPARK-15336) Detect and take action about executors running on corrupted nodes

He Tianyi created SPARK-15336:
---------------------------------

             Summary: Detect and take action about executors running on corrupted nodes
                 Key: SPARK-15336
                 URL: https://issues.apache.org/jira/browse/SPARK-15336
             Project: Spark
          Issue Type: Improvement
            Reporter: He Tianyi
            Priority: Minor


In a cluster consists of many nodes, there is a bigger chance that some corrupted nodes are running and launching containers on it. Corruptions may due to OS configuration, or file system (i.e. `python` binary corrupted in `pyspark`).
In this case, if there are one executor running on one of these nodes, one may experience a repeated task failure for tasks scheduled on that executor. 
In production, this may also leads to job failure.

Shall we provide a mechanism to detect it and do something like killing the executor?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org