hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira AJISAKA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8356) Document missing properties in hdfs-default.xml
Date Fri, 18 Mar 2016 11:25:33 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201347#comment-15201347

Akira AJISAKA commented on HDFS-8356:

Thanks [~rchiang] for updating the patch! Reviewed to "dfs.namenode.name.cache.threshold".
# Would you document that "dfs.namenode.available-space-block-placement-policy.balanced-space-preference-fraction"
is valid only if "dfs.block.replicator.classname" is set to "org.apache.hadoop.hdfs.server.blockmanagement.AvailableSpaceBlockPlacementPolicy"?
# I'm thinking "dfs.namenode.edits.dir.minimum" is the minimum number of edits dirs which
have sufficient resources for the NameNode to continue operation. Please see {{NameNodeResourcePolicy.java}}
for the detail.
# In "dfs.namenode.edits.dir.required", the description in HDFS-3677 patch is better, so I'll
commit this. Would you remove the parameter from the patch?
# "dfs.namenode.kerberos.principal" and "dfs.namenode.keytab.file" can be removed from the
patch because they are already documented.

> Document missing properties in hdfs-default.xml
> -----------------------------------------------
>                 Key: HDFS-8356
>                 URL: https://issues.apache.org/jira/browse/HDFS-8356
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.7.0
>            Reporter: Ray Chiang
>            Assignee: Ray Chiang
>              Labels: supportability, test
>         Attachments: HDFS-8356.001.patch, HDFS-8356.002.patch, HDFS-8356.003.patch, HDFS-8356.004.patch,
HDFS-8356.005.patch, HDFS-8356.006.patch, HDFS-8356.007.patch
> The following properties are currently not defined in hdfs-default.xml. These properties
should either be
> A) documented in hdfs-default.xml OR
> B) listed as an exception (with comments, e.g. for internal use) in the TestHdfsConfigFields
unit test

This message was sent by Atlassian JIRA

View raw message