[jira] Updated: (HADOOP-6812) fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.

["Konstantin Shvachko (JIRA)" <ji...@apache.org>]

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

Konstantin Shvachko updated HADOOP-6812:
----------------------------------------

    Fix Version/s: 0.22.0

> fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-6812
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6812
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.20.2, 0.21.0, 0.22.0
>            Reporter: Edward Capriolo
>             Fix For: 0.22.0
>
>         Attachments: M1726-0.patch, M1726-0v20.patch
>
>
> http://hadoop.apache.org/common/docs/current/cluster_setup.html
> fs.inmemory.size.mb does not appear in any xml file
> {noformat}
> grep "fs.inmemory.size.mb" ./mapred/mapred-default.xml 
> [edward@ec src]$ grep "fs.inmemory.size.mb" ./hdfs/hdfs-default.xml 
> [edward@ec src]$ grep "fs.inmemory.size.mb" ./core/core-default.xml 
> {noformat}
> http://hadoop.apache.org/common/docs/current/cluster_setup.html
> Documentation error:
> Real-World Cluster Configurations
> {noformat}
> conf/core-site.xml  	io.sort.factor  	100  	More streams merged at once while sorting files.
> conf/core-site.xml 	io.sort.mb 	200 	Higher memory-limit while sorting data.
> {noformat}
> core --- io.sort.factor					-- should be mapred
> core --- io.sort.mb					-- should be mapred

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