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

FTDC shouldn't conflict with secondary application

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.14
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.2
    • Sprint:
      Repl 2016-09-19

      Description

      Currently FTDC doesn't declare that it can bypass the PBWM lock. This has two effects: replication can't apply while FTDC is running (minor), FTDC can't capture data while replication is applying (potentially major). Since some replication batches such as index builds take a long time, this can result in large holes in FTDC data.

        Attachments

          Issue Links

          is depended on by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-26006 Audit all background tasks and decide which should conflict with replication application

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-37313 FTDC collection blocked during foreground index build on secondary

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

            Activity

              People

              Assignee:
              redbeard0531 Mathias Stearn
              Reporter:
              redbeard0531 Mathias Stearn
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: