GitHub user liyezhang556520 opened a pull request: https://github.com/apache/spark/pull/3824
[SPARK-4989][CORE] avoid wrong eventlog conf cause cluster down in standalone mode 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. You can merge this pull request into a Git repository by running: $ git pull https://github.com/liyezhang556520/spark wrongConf4Cluster Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/3824.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3824 ---- commit 5c1fa33799bc503ac1e2d5e9838e8e364bf1f61f Author: Zhang, Liye <liye.zh...@intel.com> Date: 2014-12-26T08:23:53Z cache exceptions when eventlog with wrong conf commit 12eee8590fb9899c267b29d3a129a169b6cf6ec1 Author: Zhang, Liye <liye.zh...@intel.com> Date: 2014-12-26T08:49:04Z add more message in log and on webUI ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org