Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 34931 invoked from network); 5 Nov 2010 06:09:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Nov 2010 06:09:57 -0000 Received: (qmail 50100 invoked by uid 500); 5 Nov 2010 06:10:29 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 50045 invoked by uid 500); 5 Nov 2010 06:10:28 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 50037 invoked by uid 99); 5 Nov 2010 06:10:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 06:10:28 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 06:10:27 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA56A7mr029956 for ; Fri, 5 Nov 2010 06:10:07 GMT Message-ID: <7853948.25011288937407520.JavaMail.jira@thor> Date: Fri, 5 Nov 2010 02:10:07 -0400 (EDT) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Commented: (HADOOP-6812) fs.inmemory.size.mb not listed in conf. Cluster setup page gives wrong advice. In-Reply-To: <1859905315.553281269879147219.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-6812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928500#action_12928500 ] Hadoop QA commented on HADOOP-6812: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12442759/M1726-0v20.patch against trunk revision 1031422. +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require tests. -1 patch. The patch command could not apply the patch. Console output: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/32//console This message is automatically generated. > 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 > 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.