hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-6493) Change dfs.namenode.startup.delay.block.deletion to second instead of millisecond
Date Thu, 03 Jul 2014 20:04:34 GMT

     [ https://issues.apache.org/jira/browse/HDFS-6493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Wang updated HDFS-6493:
------------------------------

          Resolution: Fixed
       Fix Version/s: 2.5.0
    Target Version/s: 2.5.0
              Status: Resolved  (was: Patch Available)

Committed to trunk, branch-2, branch-2.5. I wanted this in for 2.5 since it changes a config
name that hasn't been released yet.

Thanks for the patch Juan!

> 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
>             Fix For: 2.5.0
>
>         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)

Mime
View raw message