hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8689) Make trash a server side configuration option
Date Fri, 17 Aug 2012 23:26:38 GMT

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

Eli Collins updated HADOOP-8689:

          Resolution: Fixed
       Fix Version/s: 2.2.0-alpha
    Target Version/s:   (was: 2.2.0-alpha)
        Hadoop Flags: Incompatible change,Reviewed  (was: Incompatible change)
              Status: Resolved  (was: Patch Available)

Thanks for the review ATM.  I've committed this and merged to branch-2.
> Make trash a server side configuration option
> ---------------------------------------------
>                 Key: HADOOP-8689
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8689
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>             Fix For: 2.2.0-alpha
>         Attachments: hadoop-8689.txt, hadoop-8689.txt
> Per ATM's suggestion in HADOOP-8598 for v2 let's make {{fs.trash.interval}} configured
server side. If it is not configured server side then the client side configuration is used.
The {{fs.trash.checkpoint.interval}} option is already server side as the emptier runs in
the NameNode. Clients may manually run an emptier via hadoop org.apache.hadoop.fs.Trash but
it's OK if it uses a separate interval. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message