Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Invalid
    • Affects Version/s: 0.99.0
    • Fix Version/s: 0.99.0
    • Component/s: wal
    • Labels:
      None

      Description

      This was found by Jeffrey Zhong See parent issue. We have this issue since we put the ring buffer/disrupter into the WAL (HBASE-10156).

      An edits region sequence id is set only after the edit has traversed the ring buffer. Flushing, we just up whatever the current region sequence id is. Crossing the ring buffer may take some time and is done by background threads. The flusher may be taking the region sequence id though edits have not yet made it across the ringbuffer: i.e. edits that are actually scoped by the flush may have region sequence ids in excess of that of the flush sequence id reported.

      The consequences are not exactly clear. Would rather not have to find out so lets fix this here.

      1. 11109v2.txt
        28 kB
        stack
      2. 11109v2.txt
        28 kB
        stack
      3. 11109.txt
        6 kB
        stack

        Issue Links

          Activity

            People

            • Assignee:
              stack
              Reporter:
              stack
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development