Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 12 Jul 2012 20:43:34 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <392734811.43979.1342125814866.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1367562225.43251.1342118735154.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Assigned] (HDFS-3647) Backport HDFS-2868 (Add number of
 active transfer threads to the DataNode status) to branch-1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J reassigned HDFS-3647:
-----------------------------

    Assignee: Harsh J
    
> Backport HDFS-2868 (Add number of active transfer threads to the DataNode status) to branch-1
> ---------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3647
>                 URL: https://issues.apache.org/jira/browse/HDFS-3647
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node, performance
>    Affects Versions: 0.20.2
>            Reporter: Steve Hoffman
>            Assignee: Harsh J
>
> Not sure if this is in a newer version of Hadoop, but in CDH3u3 it isn't there.
> There is a lot of mystery surrounding how large to set dfs.datanode.max.xcievers.  Most people say to just up it to 4096, but given that exceeding this will cause an HBase RegionServer shutdown (see Lars' blog post here: http://www.larsgeorge.com/2012/03/hadoop-hbase-and-xceivers.html), it would be nice if we could expose the current count via the built-in metrics framework (most likely under dfs).  In this way we could watch it to see if we have it set too high, too low, time to bump it up, etc.
> Thoughts?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira