Test dbCheck with lagged secondary and writeConcern: n

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We have seen in a few HELP cases that dbCheck causes asymmetric replication lag on one secondary. In these cases, a common recommendation is to set batchWriteConcern: n = # of replicating nodes in the set. This is to effectively throttle dbCheck and prevent further batches from being executed until the lagged secondary catches up We should add a test to cover this case and verify that this behavior is as expected.

            Assignee:
            Unassigned
            Reporter:
            Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: