[
https://issues.apache.org/jira/browse/HDFS-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201944#comment-13201944
]
Aaron T. Myers commented on HDFS-2781:
--------------------------------------
bq. What do you mean by parse error?
Sorry, calling it a "parse error" isn't quite accurate. I've just always found
it a little suspect that DF returns 0 for space available if the given path
doesn't exist. It should probably throw an error or something along those lines.
Also, note that the NameNodeResourceChecker can't really be considered helpful
in this case, since it runs asynchronously. i.e. the NN might continue not in
SM for a while (a minute by default, I think) before the NNResourceChecker runs
and moves the NN into SM.
> 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
