hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3645) Improve the way we do detection of a busy DN in the cluster, when choosing it for a block write
Date Thu, 12 Jul 2012 16:54:34 GMT

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

Suresh Srinivas commented on HDFS-3645:
---------------------------------------

bq. a more realistic measure of if a DN is really busy by itself
Can you elaborate on what this means. Without comparing it with other DNs available in the
cluster, a local state of DN is incomplete, no?
                
> Improve the way we do detection of a busy DN in the cluster, when choosing it for a block
write
> -----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3645
>                 URL: https://issues.apache.org/jira/browse/HDFS-3645
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 2.0.0-alpha
>            Reporter: Harsh J
>            Priority: Minor
>
> Right now, I think we do too naive a computation for detecting if a chosen DN target
is busy by itself. We currently do {{node.getXceiverCount() > (2.0 * avgLoad)}}.
> We should improve on this computation with a more realistic measure of if a DN is really
busy by itself or not (rather than checking against cluster average, where there's a good
chance the value can be wrong to compare with, for some cases)

--
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