[
https://issues.apache.org/jira/browse/HDFS-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3647.
---------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Target Version/s: (was: 1.2.0)
Hadoop Flags: Reviewed
Thanks Todd, I've committed this backport to branch-1.
> 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
> Fix For: 1.2.0
>
> Attachments: HDFS-3647.patch, Screen Shot 2012-07-14 at 12.41.07
> AM.png
>
>
> 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
