Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06E8C90C8 for ; Wed, 30 May 2012 12:04:26 +0000 (UTC) Received: (qmail 59879 invoked by uid 500); 30 May 2012 12:04:25 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 59651 invoked by uid 500); 30 May 2012 12:04:25 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 59602 invoked by uid 99); 30 May 2012 12:04:24 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2012 12:04:24 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 7EE7F140C2C for ; Wed, 30 May 2012 12:04:24 +0000 (UTC) Date: Wed, 30 May 2012 12:04:24 +0000 (UTC) From: "Harsh J (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <367081840.15807.1338379464522.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (HDFS-3475) Make the replication monitor multipliers configurable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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