hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-3475) Make the replication monitor multipliers configurable
Date Wed, 30 May 2012 12:04:22 GMT
Harsh J created HDFS-3475:
-----------------------------

             Summary: Make the replication monitor multipliers configurable
                 Key: HDFS-3475
                 URL: https://issues.apache.org/jira/browse/HDFS-3475
             Project: Hadoop HDFS
          Issue Type: Improvement
    Affects Versions: 3.0.0
            Reporter: Harsh J
            Assignee: Harsh J
            Priority: Trivial


BlockManager currently hardcodes the following two constants:

{code}
private static final int INVALIDATE_WORK_PCT_PER_ITERATION = 32;
private static final int REPLICATION_WORK_MULTIPLIER_PER_ITERATION = 2;
{code}

These are used to throttle/limit the amount of deletion and replication-to-other-DN work done
per heartbeat interval of a live DN.

Not many have had reasons to want these changed so far but there have been a few requests
I've faced over the past year from a variety of clusters I've helped maintain. I think with
the improvements in disks and network thats already started to be rolled out in production
environments out there, changing these may start making sense to some.

Lets at least make it advanced-configurable with proper docs that warn adequately, with the
defaults being what they are today. With hardcodes, it comes down to a recompile for admins,
which is not something they may like.

Please let me know your 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