[
https://issues.apache.org/jira/browse/SPARK-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved SPARK-18119.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request 15648
[https://github.com/apache/spark/pull/15648]
> Namenode safemode check is only performed on one namenode which can stuck the
> startup of SparkHistory server
> ------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-18119
> URL: https://issues.apache.org/jira/browse/SPARK-18119
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.6.2, 2.0.1
> Environment: HDFS cdh 5.5.0 with HA namenode
> Reporter: Nicolas Fraison
> Priority: Minor
> Fix For: 2.1.0
>
>
> SparkHistory server startup is stuck when one of the 2 HA namenode is in
> safemode displaying this log message: HDFS is still in safe mode. Waiting...
> This happens even if one of the 2 namenode is in active mode because it only
> request the first one of 2 available namenode in an HA configuration
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
