Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-21504

If enable FIFOCompactionPolicy, a compaction may write a "empty" hfile whose maxTimeStamp is long max. This kind of hfile will never be archived.

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Reviewed

    Description

      When i use FIFOCompactionPolicy, and if all hfiles(>1) are TTL expired in a region, once we do a compaction on the region, the compaction policy will select the latest hfile to do compaction.But beacuse the latest hfile is already TTL expired, compactor only write a "empty" hfile(whose entry counter is 0 and maxTimeStamp is Long.MAX_VALUE) finally. Because maxTimeStamp is long max, so the "empty" hfile will never be TTL expired, more seriously we can not archive it by FIFOCompactionPolicy forever.

      Attachments

        1. HBASE-21504.v1.patch
          7 kB
          Zheng Hu
        2. 1.patch
          3 kB
          xuming

        Activity

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

          People

            openinx Zheng Hu
            xuming xuming
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment