hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Hoffman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3647) Expose current xcievers count as metric
Date Thu, 12 Jul 2012 19:01:35 GMT

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

Steve Hoffman commented on HDFS-3647:
-------------------------------------

https://issues.cloudera.org/browse/DISTRO-414 opened with cloudera.  Thx.

I'll leave it to you guys if you want to use this to track a 1.X apache back port.
                
> Expose current xcievers count as metric
> ---------------------------------------
>
>                 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
>
> 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

        

Mime
View raw message