You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2014/07/03 22:02:34 UTC
[jira] [Updated] (HDFS-6493) Change
dfs.namenode.startup.delay.block.deletion to second instead of millisecond
[ https://issues.apache.org/jira/browse/HDFS-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated HDFS-6493:
------------------------------
Summary: Change dfs.namenode.startup.delay.block.deletion to second instead of millisecond (was: Propose to change "dfs.namenode.startup.delay.block.deletion" to second instead of millisecond)
> 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
> Attachments: HDFS-6493.001.patch
>
>
> 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)