FTDC shouldn't conflict with secondary application

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.14
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • v3.2
    • Repl 2016-09-19
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

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

              Created:
              Updated:
              Resolved: