[
https://issues.apache.org/jira/browse/HDFS-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Chu updated HDFS-5701:
------------------------------
Attachment: HDFS-5701.patch
Single character change to make maxttl -> maxTtl.
No unit tests needed for this small usage fix.
> 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
> 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)
