Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-89659

Fix jsTests that could intermittently fail with staleConfig after shardCollection

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2024-04-29, CAR Team 2024-05-13
    • 200
    • 2

      A direct connection to a shard could fail with staleConfig after SERVER-80135 since shardCollection information refresh has been converted from sync to async. If a direct connection ends up using stale information, the command fails with the sharding status of collection XYZ Is not currently known and needs to be recovered.

      The fix is to not use the direct connection, or do something before to force a refresh.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: