Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-40120

Incorrect PageBytes and ItemCnt after recovery

    XMLWordPrintable

    Details

    • Triage:
      Untriaged
    • Story Points:
      1
    • Is this a Regression?:
      No

      Description

      Log replay will skip data blocks if a more recent header was already recovered by checkpoint recovery. But, during skipping of stale data block, we do not clear page op stats due to that stale data block. These stats get accumulated on the next UpdateMapping for the gCtx. This leads to larger values for stats like PageBytes and ItemCnt after recovery.

        Attachments

          Issue Links

          backports to

          Bug - A problem which impairs or prevents the functions of the product. MB-41646 BP 6.6.x MB-40120 Incorrect PageBytes and ItemCnt after recovery

          • Major - Major loss of function.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            build-team Couchbase Build Team added a comment -

            Build couchbase-server-7.0.0-2568 contains plasma commit d0b6706 with commit message:
            MB-40120: Discard page ops during log replay

            Show
            build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-2568 contains plasma commit d0b6706 with commit message: MB-40120 : Discard page ops during log replay
            Hide
            Permalink
            girish.benakappa Girish Benakappa added a comment -

            Akhil Mundroy Can this be verified by code instrumentation as you did in 6.6 ?

            Show
            girish.benakappa Girish Benakappa added a comment - Akhil Mundroy Can this be verified by code instrumentation as you did in 6.6 ?
            Hide
            Permalink
            srinath.duvuru Srinath Duvuru added a comment -

            The back port was straight forward and the fix was verified in back port. We can close this.

            Show
            srinath.duvuru Srinath Duvuru added a comment - The back port was straight forward and the fix was verified in back port. We can close this.

              People

              Assignee:
              akhil.mundroy Akhil Mundroy
              Reporter:
              akhil.mundroy Akhil Mundroy
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes

                    PagerDuty