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

Combine MVCC and SeqId

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

Details

    • Improvement
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • None
    • 0.99.0
    • regionserver
    • None
    • Reviewed

    Description

      HBASE-8701 and a lot of recent issues include good discussions about mvcc + seqId semantics. It seems that having mvcc and the seqId complicates the comparator semantics a lot in regards to flush + WAL replay + compactions + delete markers and out of order puts.

      Thinking more about it I don't think we need a MVCC write number which is different than the seqId. We can keep the MVCC semantics, read point and smallest read points intact, but combine mvcc write number and seqId. This will allow cleaner semantics + implementation + smaller data files.

      We can do some brainstorming for 0.98. We still have to verify that this would be semantically correct, it should be so by my current understanding.

      Attachments

        Issue Links

        Activity

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

          People

            jeffreyz Jeffrey Zhong Assign to me
            enis Enis Soztutar
            Votes:
            0 Vote for this issue
            Watchers:
            31 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment