Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Tue, 4 Mar 2014 08:07:23 +0000 (UTC)
From: "Mingjiang Shi (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12698584.1393920433438.8736.1393920443548@arcas>
In-Reply-To: <JIRA.12698584.1393920433438@arcas>
References: <JIRA.12698584.1393920433438@arcas>
Subject: [jira] [Created] (HADOOP-10381) Support unit suffix in the
 configuration values
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Mingjiang Shi created HADOOP-10381:
--------------------------------------

             Summary: Support unit suffix in the configuration values 
                 Key: HADOOP-10381
                 URL: https://issues.apache.org/jira/browse/HADOOP-10381
             Project: Hadoop Common
          Issue Type: Improvement
          Components: conf
    Affects Versions: 2.3.0
            Reporter: Mingjiang Shi


*Background*
Currently, most configuration values implicitly indicate the unit, for example:
- dfs.namenode.delegation.key.update-interval, the unit is milliseconds,
- dfs.ha.log-roll.period, the unit is seconds
- dfs.datanode.du.reserved, the unit is bytes

*This causes a few inconveniences*
1. When modify a configuration file, one need to refer to the document to find out the expected unit, convert from the human readable unit to the expect unit. Otherwise, wrong value may be configured.
2. While reviewing the configuration file, it'll take some time to figure out the human readable size of a large number.  For example, 134217728 is actually 128MB

*Proposal*
For any space or time related configurations, it should allow include the unit suffix, for example:
- space related units: 64k, 64kb, 128m, 128mb, 1g, 1gb
- time related units: 1000ms, 1min, 60sec, 1hour

If no unit suffix is given, the default unit for the configuration item is used.


--
This message was sent by Atlassian JIRA
(v6.2#6252)