Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-18751 Revisit the TimeRange and TimeRangeTracker
  3. HBASE-18966

Use non-sync TimeRangeTracker as a replacement for TimeRange in ImmutableSegment

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.0.0-beta-1, 2.0.0
    • None
    • None
    • Reviewed

    Description

      The in-memory compaction/merge updates only the TimeRangeTracker when creating new ImmutableSegment, but the time information used to do time filter is the TimeRange rather than TimeRangeTracker. It don't cause any bugs currently because the TimeRange is used for store-level ts filter only and the default TimeRange of ImmutableSegment created by in-memory compaction/merge has the maximum ts range.

      The TimeRange was used to be a snapshot of TimeRangeTracker for avoiding the sync operation happening in TimeRangeTracker. We can use non-sync trt introduced by HBASE-18753 to replace the TimeRange.

      Attachments

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

          People

            chia7712 Chia-Ping Tsai Assign to me
            chia7712 Chia-Ping Tsai
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment