Flow control lag check can report isLagged as false even though lag is large if operations are sparse

XMLWordPrintableJSON

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

      In instances where few operations cause large replication lag (e.g., due to an unresponsive secondary), Flow Control's lag check can report isLagged to be false. This could be due to a bug in _approximateOpsBetween. The work for this ticket should be to investigate the behavior of the isLagged check in this scenario.

            Assignee:
            Unassigned
            Reporter:
            Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: