You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Greg Roelofs (JIRA)" <ji...@apache.org> on 2011/01/04 21:46:48 UTC

[jira] Commented: (HADOOP-7080) Documentation dfs.block.size where dfs.blocksize has to be used instead.

    [ https://issues.apache.org/jira/browse/HADOOP-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977452#action_12977452 ] 

Greg Roelofs commented on HADOOP-7080:
--------------------------------------

I looked into this a bit on 0.22(ish) while trying to test another feature (in early November, I think?).  At the time, dfs.blocksize was used in:

{noformat}
    hdfs-default.xml
    hdfs/DFSConfigKeys.java
    hdfs/server/namenode/TestHDFSConcat.java
{noformat}

dfs.block.size was used in:

{noformat}
    Hadoop FAQ
    hadoop-hdfs/src/c++/libhdfs/hdfs.c 
    hdfsproxy-default.xml
    documentation/content/xdocs/hdfsproxy.xml
    hdfs/HdfsConfiguration.java
    fs/TestFiRename.java
    hdfs/server/namenode/TestBlockTokenWithDFS.java
    hdfs/TestFileConcurrentReader.java
{noformat}

(I realize the paths are incomplete; so are my notes at this point.)

Perhaps this JIRA should be under HDFS rather than common?

> Documentation dfs.block.size where dfs.blocksize has to be used instead.
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-7080
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7080
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>         Environment: Linux (Ubuntu)
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>
> The configuration for the block size is named *dfs.block.size* in the [documentation for Release 0.21.0 of Hadoop|http://hadoop.apache.org/common/docs/r0.21.0/cluster_setup.html] but this will not work nor will it be recognized. If i use [*dfs.blocksize*|http://hadoop.apache.org/hdfs/docs/current/api/constant-values.html] instead it will work perfectly.  So this seemed to be a documentation bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.