You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Zhang, Liye (JIRA)" <ji...@apache.org> on 2014/12/29 15:39:13 UTC
[jira] [Comment Edited] (SPARK-4989) wrong application
configuration cause cluster down in standalone mode
[ https://issues.apache.org/jira/browse/SPARK-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259938#comment-14259938 ]
Zhang, Liye edited comment on SPARK-4989 at 12/29/14 2:39 PM:
--------------------------------------------------------------
A following up JIRA is opened for resolving the Cluster resume. Please see [SPARK-4891|https://issues.apache.org/jira/browse/SPARK-4991]
was (Author: liyezhang556520):
An following JIRA is opened for resolving the Cluster resume. Please see [SPARK-4891|https://issues.apache.org/jira/browse/SPARK-4991]
> 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
>
> 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