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

Aleksandr Kovalenko commented on AMBARI-11430:
----------------------------------------------

+1 for the patch

> fs.trash.Interval -- Tooltip is wrong -- or label is wrong
> ----------------------------------------------------------
>
>                 Key: AMBARI-11430
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11430
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11430.patch, Screen Shot 2015-05-20 at 3.55.07 
> PM.png
>
>
> Under Ambari - we have a setting - fs.trash.interval -- but the help tooltip 
> says *Number of minutes between trash checkpoints.* instead of *Number of 
> minutes after which the checkpoint gets deleted* .
> First make sure that setting is not labeled wrongly, if it is not, then 
> update the help text.
> if not, then the Label of the text needs to be fixed.
> ||Heading 1||Heading 2||Heading 3||
> |fs.trash.interval|0|Number of minutes after which the checkpoint gets 
> deleted. If zero, the trash feature is disabled. This option may be 
> configured both on the server and the client. If trash is disabled server 
> side then the client side configuration is checked. If trash is enabled on 
> the server side then the value configured on the server is used and the 
> client configuration value is ignored.|
> |fs.trash.checkpoint.interval|0|Number of minutes between trash checkpoints. 
> Should be smaller or equal to fs.trash.interval. If zero, the value is set to 
> the value of fs.trash.interval. Every time the checkpointer runs it creates a 
> new checkpoint out of current and removes checkpoints created more than 
> fs.trash.interval minutes ago.



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

Reply via email to