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] [Commented] (HDFS-5701) Fix the CacheAdmin -addPool -maxTtl option name
Date Mon, 30 Dec 2013 19:59:51 GMT

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

Andrew Wang commented on HDFS-5701:
-----------------------------------

+1 thanks Stephen. Will commit shortly.

> Fix the CacheAdmin -addPool -maxTtl option name
> -----------------------------------------------
>
>                 Key: HDFS-5701
>                 URL: https://issues.apache.org/jira/browse/HDFS-5701
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: caching, tools
>    Affects Versions: 3.0.0
>            Reporter: Stephen Chu
>            Assignee: Stephen Chu
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: HDFS-5701.patch
>
>
> Currently, the CacheAdmin usage shows the "maxttl" option for -addPool, but the option
should be listed as "maxTtl" instead.
> If users attempt to use "maxttl" they will see the following error:
> {code}
> bash-4.1$ hdfs cacheadmin -addPool pool2 -maxttl 10s
> Can't understand arguments: -maxttl 10s
> Usage is [-addPool <name> [-owner <owner>] [-group <group>] [-mode
<mode>] [-limit <limit>] [-maxttl <maxTtl>]
> {code}
> We should change the usage to usage "maxTtl"



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message