Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 7 May 2011 10:33:03 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1373564442.29997.1304764383443.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1774560346.6656.1303928403222.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1866) Document
 dfs.datanode.max.transfer.threads in hdfs-default.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030308#comment-13030308 ] 

Hadoop QA commented on HDFS-1866:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12478500/HDFS-1866.r1.diff
  against trunk revision 1100279.

    +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://builds.apache.org/hudson/job/PreCommit-HDFS-Build/465//console

This message is automatically generated.

> Document dfs.datanode.max.transfer.threads in hdfs-default.xml
> --------------------------------------------------------------
>
>                 Key: HDFS-1866
>                 URL: https://issues.apache.org/jira/browse/HDFS-1866
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node, documentation
>            Reporter: Eli Collins
>            Assignee: Harsh J Chouraria
>            Priority: Minor
>             Fix For: 0.22.0
>
>         Attachments: HDFS-1866.r1.diff
>
>
> dfs.datanode.max.transfer.threads (formerly dfs.datanode.max.xcievers) should be covered in hdfs-default.xml.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira