Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-8689

Make trash a server side configuration option

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0.0-alpha
    • 2.0.2-alpha
    • fs
    • None
    • Incompatible change, Reviewed
    • If fs.trash.interval is configured on the server then the client's value for this configuration is ignored.

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            eli Eli Collins Assign to me
            eli Eli Collins
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment