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 "Lin Yiqun (JIRA)" <ji...@apache.org> on 2016/04/01 03:56:25 UTC

[jira] [Commented] (HDFS-9847) HDFS configuration without time unit name should accept friendly time units

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

Lin Yiqun commented on HDFS-9847:
---------------------------------

Update the patch nothrow-004 with leaving the defaults in hdfs-default.xml. The code in hadoop main source and unit tests should be ok because it has tested in nothow-003 patch which was changing the defaults with time unit.

> HDFS configuration without time unit name should accept friendly time units
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-9847
>                 URL: https://issues.apache.org/jira/browse/HDFS-9847
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: 2.7.1
>            Reporter: Lin Yiqun
>            Assignee: Lin Yiqun
>         Attachments: HDFS-9847-branch-2.001.patch, HDFS-9847-branch-2.002.patch, HDFS-9847-nothrow.001.patch, HDFS-9847-nothrow.002.patch, HDFS-9847-nothrow.003.patch, HDFS-9847-nothrow.004.patch, HDFS-9847.001.patch, HDFS-9847.002.patch, HDFS-9847.003.patch, HDFS-9847.004.patch, HDFS-9847.005.patch, HDFS-9847.006.patch, branch-2-delta.002.txt, timeduration-w-y.patch
>
>
> In HDFS-9821, it talks about the issue of leting existing keys use friendly units e.g. 60s, 5m, 1d, 6w etc. But there are som configuration key names contain time unit name, like {{dfs.blockreport.intervalMsec}}, so we can make some other configurations which without time unit name to accept friendly time units. The time unit  {{seconds}} is frequently used in hdfs. We can updating this configurations first.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)