Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
Sharding EMEA 2022-03-21
-
155
Description
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.
Attachments
Issue Links
- is caused by
-
SERVER-63327 Remove usages of the StaleShardVersion error code from the migrations path
-
- Closed
-