Add unit test coverage for serverStatus.syncSource.numSyncSourceChangesDueToSignificantlyCloserNode

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • Repl 2025-05-12
    • 0
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      From SERVER-104669, incrementing this metric was being tested alongside testing the actual syncSourceChange behavior. It was causing failures (BF-37598) due to machine flakiness when the metric was being checked, even though the actual behavior was working as intended. Rather than test this metric in an integration test, we should add unit test coverage for it instead. We should also audit all usages of this metric in all js tests and just rely on the unittests for increment/decrement coverage.

            Assignee:
            Ruchitha Rajaghatta
            Reporter:
            Ruchitha Rajaghatta
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: