[
https://issues.apache.org/jira/browse/HDFS-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201849#comment-13201849
]
Aaron T. Myers commented on HDFS-2781:
--------------------------------------
bq. Actually the active goes into safe mode on my machine because it thinks
there is not enough space.
That's very likely a parsing error. As I recall, DF (as in, the Java class)
which NameNodeResourceChecker uses just quietly returns 0 for free space of a
directory that doesn't exist:
{noformat}
$ hadoop org.apache.hadoop.fs.DF /does/not/exist
df -k null
null 0 0 0 0% null
{noformat}
> Add client protocol and DFSadmin for command to restore failed storage
> ----------------------------------------------------------------------
>
> Key: HDFS-2781
> URL: https://issues.apache.org/jira/browse/HDFS-2781
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Eli Collins
> Assignee: Eli Collins
>
> Per HDFS-2769, it's important that an admin be able to ask the NN to try to
> restore failed storage since we may drop into SM until the shared edits dir
> is restored (w/o having to wait for the next checkpoint). There's currently
> an API (and usage in DFSAdmin) to flip the flag indicating whether the NN
> should try to restore failed storage but not that it should actually attempt
> to do so. This jira is to add one. This is useful outside HA but doing as an
> HDFS-1623 sub-task since it's motivated by HA.
--
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
