GitHub user ashangit opened a pull request:
https://github.com/apache/spark/pull/15648
[SPARK-18119][SPARK-CORE] Namenode safemode check is only performed on one
namenode which can stuck the startup of SparkHistory server
## What changes were proposed in this pull request?
Instead of using the setSafeMode method that check the first namenode used
the one which permitts to check only for active NNs
## How was this patch tested?
manual tests
Please review
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark before
opening a pull request.
This commit is contributed by Criteo SA under the Apache v2 licence.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/criteo-forks/spark SPARK-18119
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/15648.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 #15648
----
commit 501dd4848a2dfd615a44c67274922ca7345f6323
Author: n.fraison <n.frai...@criteo.com>
Date: 2016-10-26T19:11:03Z
[SPARK-18119][SPARK-CORE] Namenode safemode check is only performed on one
namenode which can stuck the startup of SparkHistory server
This commit is contributed by Criteo SA under the Apache v2 licence.
----
---
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
