[ 
https://issues.apache.org/jira/browse/HDFS-11049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira Ajisaka updated HDFS-11049:
---------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0-alpha2
                   2.9.0
           Status: Resolved  (was: Patch Available)

Committed this to trunk and branch-2. Thanks [~linyiqun] for the contribution!

> The description of dfs.block.replicator.classname is not clear
> --------------------------------------------------------------
>
>                 Key: HDFS-11049
>                 URL: https://issues.apache.org/jira/browse/HDFS-11049
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Yiqun Lin
>            Assignee: Yiqun Lin
>            Priority: Minor
>             Fix For: 2.9.0, 3.0.0-alpha2
>
>         Attachments: HDFS-11049.001.patch, HDFS-11049.002.patch
>
>
> Now the description of the property {{dfs.block.replicator.classname}} seems 
> not clearly. The current description:
> {code}
> <property>
>   <name>dfs.block.replicator.classname</name>  
> <value>org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicyDefault</value>
>   <description>
>     Class representing block placement policy for non-striped files.
>   </description>
> </property>
> {code}
> It seems too simple and the users will not get the other available block 
> placement policies and its usage. For example in HDFS-7541, it introduced     
> a new policy {{BlockPlacementPolicyWithUpgradeDomain}}. This policy can be 
> good used in rolling upgrade opeations.
> In addition, I don't find other documentations that concretely introducing 
> the existing placement policies. This JIRA foucus on making a improvement for 
> this in file {{hdfs-default.xml}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to