[
https://issues.apache.org/jira/browse/HDFS-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153363#comment-13153363
]
Eli Collins commented on HDFS-2430:
-----------------------------------
The api for NNResourcePolicy#areResourcesAvailable is a little strange, if a
required resource is not available we return false, but if there are not enough
redundant resources we throw a RTE. Do callers need to distinguish between
these two cases? If not, we should return false in both cases.
If so, there should be two separate apis. I'd make the method name better
reflect the purpose in the comment (whether we can log edits), the method is
generic but the particular policy is edits-specific.
Does the dir checking use canonical paths so we're sure the checks pass in case
of symlinks?
Nits:
* NNResourcePolicy needs param javadocs
* NNResourcePolicy, NNResourceChecker, and CheckableNNResource need
@InterfaceAudience.Private annotations
Otherwise looks great.
> The number of failed or low-resource volumes the NN can tolerate should be
> configurable
> ---------------------------------------------------------------------------------------
>
> Key: HDFS-2430
> URL: https://issues.apache.org/jira/browse/HDFS-2430
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: name-node
> Affects Versions: 0.24.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: HDFS-2430.patch, HDFS-2430.patch, HDFS-2430.patch
>
>
> Currently the number of failed or low-resource volumes the NN can tolerate is
> effectively hard-coded at 1. It would be nice if this were configurable.
--
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
