Pre-warm router role cache in reap_sessions_with_active_yielders.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This test expects an internal transaction using the router role on a shard to remote target a specific number of times, which requires the shard's router shard version cache to be up to date, otherwise a stale cache can trigger a retry. Ideally this test shouldn't require a specific number of attempts, but as a short term fix, update the test to pre-warm the cache to avoid retries. This is only a problem now that the router and shard caches were split by SERVER-95393.

              Assignee:
              Jack Mulrow
              Reporter:
              Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: