RetryableInternalTransactionTest should explicitly wait for the ReplicaSetMonitor on all mongoses to have detected the new primary after failover or restart

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • Cluster Scalability 2025-03-17
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The setUpTestMode helper in retryable_internal_transaction_test.js is already waiting for the primary. However, that appears to be not sufficient when the SDAM ReplicaSetMonitor is used. I think we could solve this by explicitly wait for the RSM on the mongoses to detect the new primary, for example, by calling awaitRSClientHosts like in this test.

            Assignee:
            Cheahuychou Mao
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: