hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-6664) fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.
Date Mon, 29 Mar 2010 18:11:27 GMT

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

Chris Douglas resolved HADOOP-6664.
-----------------------------------

    Resolution: Invalid

> fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-6664
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6664
>             Project: Hadoop Common
>          Issue Type: Task
>          Components: conf, documentation
>    Affects Versions: 0.20.2
>            Reporter: Edward Capriolo
>
> 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.


Mime
View raw message