Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-28988

add ReplicationProcess and use it to cache Rollback ID

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.7
    • Component/s: Replication
    • Labels:
      None

      Description

      As part of SERVER-27659 we moved from an in-memory rbid to one stored in a collection, which requires a global IS lock. This makes commands that didn't used to require any global lock require one to fill in the replSet metadata. This seems to be causing spurious stepdowns in some of our tests. Additionally, it prevents FTDC from capturing data while the global lock is held or pending.

        Attachments

          Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-28218 Recoverable Rollback: Implement Rollback Progress

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-27659 persist Rollback ID and read it at startup

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-32776 Refresh rollback id cache on increment

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              benety.goh Benety Goh
              Reporter:
              redbeard0531 Mathias Stearn
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: