[
https://issues.apache.org/jira/browse/HDFS-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293192#comment-13293192
]
Aaron T. Myers commented on HDFS-3518:
--------------------------------------
bq. I think this is different from HDFS-2413. Not in SafeMode is necessary
condition but not a sufficient condition of being operational. For example, if
a namenode is standby but not in safemode, it is not operational. How about add
a new method, say isHealth(URI), as a public API?
Seems like the solution to that problem, then, is just to fix HDFS-3507, which
would make DFS#isInSafeMode perform client failover.
> Provide API to check HDFS operational state
> -------------------------------------------
>
> Key: HDFS-3518
> URL: https://issues.apache.org/jira/browse/HDFS-3518
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Reporter: Bikas Saha
> Assignee: Tsz Wo (Nicholas), SZE
>
> This will improve the usability of JobTracker safe mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
