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

Posted to issues@spark.apache.org by "sam (JIRA)" <ji...@apache.org> on 2014/06/05 11:48:02 UTC

[jira] [Comment Edited] (SPARK-2019) Spark workers die/disappear when job fails for nearly any reason

    [ https://issues.apache.org/jira/browse/SPARK-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018048#comment-14018048 ] 

sam edited comment on SPARK-2019 at 6/5/14 9:47 AM:
----------------------------------------------------

Sorry. Its -0.9.1- 0.9.0


was (Author: sams):
Sorry. Its 0.9.1

> Spark workers die/disappear when job fails for nearly any reason
> ----------------------------------------------------------------
>
>                 Key: SPARK-2019
>                 URL: https://issues.apache.org/jira/browse/SPARK-2019
>             Project: Spark
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: sam
>            Priority: Critical
>
> We either have to reboot all the nodes, or run 'sudo service spark-worker restart' across our cluster.  I don't think this should happen - the job failures are often not even that bad.  There is a 5 upvoted SO question here: http://stackoverflow.com/questions/22031006/spark-0-9-0-worker-keeps-dying-in-standalone-mode-when-job-fails
> We shouldn't be giving restart privileges to our devs, and therefore our sysadm has to frequently restart the workers.  When the sysadm is not around, there is nothing our devs can do.
> Many thanks



--
This message was sent by Atlassian JIRA
(v6.2#6252)