[5.0] Make shard registry reads fallback to majority readConcern if snapshot reads fail

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.26
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2024-03-04
    • 156
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With SERVER-85869 we made it so that shard registry reads would exclusively use snapshot readConcern. However, in a mixed version cluster with 5.0 and 4.4 the operation will fail as snapshot reads outside of a transaction weren't supported there.

      As a result we should make the operation retry the operation with majority reads if it receives an InvalidOptions error.

            Assignee:
            Jordi Olivares Provencio
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: