Wait for db critical section on StaleDbVersion

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-03-21
    • 155
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-63327 we swapped the order of checks performed in DatabaseShardingState::checkDbVersion. If we don't currently know the version for a db we now throw StaleDbVersion ignoring the db critical section, even if a critical section is actually in place for that db.

      This means that we will possibly perform a refresh and retry the command locally on the shard even if the db critical section is taken.

              Assignee:
              Kaloian Manassiev
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: