spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Or (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SPARK-4989) wrong application configuration cause cluster down in standalone mode
Date Thu, 08 Jan 2015 18:42:34 GMT

     [ https://issues.apache.org/jira/browse/SPARK-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Or updated SPARK-4989:
-----------------------------
    Fix Version/s: 1.3.0

> wrong application configuration cause cluster down in standalone mode
> ---------------------------------------------------------------------
>
>                 Key: SPARK-4989
>                 URL: https://issues.apache.org/jira/browse/SPARK-4989
>             Project: Spark
>          Issue Type: Bug
>          Components: Deploy, Spark Core
>    Affects Versions: 1.0.0, 1.1.0, 1.2.0
>            Reporter: Zhang, Liye
>            Priority: Critical
>             Fix For: 1.3.0
>
>
> when enabling eventlog in standalone mode, if give the wrong configuration, the standalone
cluster will down (cause master restart, lose connection with workers). 
> How to reproduce: just give an invalid value to "spark.eventLog.dir", for example: *spark.eventLog.dir=hdfs://tmp/logdir1,
hdfs://tmp/logdir2*. This will throw illegalArgumentException, which will cause the *Master*
restart. And the whole cluster is not available.
> This is not acceptable that cluster is crashed by one application's wrong setting.



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


Mime
View raw message