Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 10 Jun 2014 14:48:02 +0000 (UTC)
From: "Juan Yu (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12718757.1402015784302.101753.1402411682285@arcas>
In-Reply-To: <JIRA.12718757.1402015784302@arcas>
References: <JIRA.12718757.1402015784302@arcas>
Subject: [jira] [Commented] (HDFS-6493) Propose to change
 "dfs.namenode.startup.delay.block.deletion" to second instead of
 millisecond
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Juan Yu commented on HDFS-6493:
-------------------------------

Thanks for the suggestion.

> Propose to change "dfs.namenode.startup.delay.block.deletion" to second instead of millisecond
> ----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-6493
>                 URL: https://issues.apache.org/jira/browse/HDFS-6493
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Juan Yu
>            Assignee: Juan Yu
>            Priority: Trivial
>
> Based on the discussion in https://issues.apache.org/jira/browse/HDFS-6186, the delay will be at least 30 minutes or even hours. it's not very user friendly to use milliseconds when it's likely measured in hours.
> I suggest to make the following change
> 1. change the unit of this config to second
> 2. rename the config key from "dfs.namenode.startup.delay.block.deletion.ms" to "dfs.namenode.startup.delay.block.deletion.sec"
> 3. add the default value to hdfs-default.xml, what's the reasonable value, 30 minutes, one hour?


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