-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-02-24, Sharding 2020-03-09
After completion of SERVER-45778 throw Stale Shard Version if the collection data is unknown, that is, if the metadata has not been loaded yet, and if any code path is not ready to receive and handle the exception, investigate the case and handle the exception if appropiate.
- causes
-
PYTHON-2154 test_examples.TestTransactionExamples fails on 4.5-latest sharded clusters
- Closed
- depends on
-
SERVER-45778 Rename getOrphanFilter to getOwnershipFilter and change the return type
- Closed
-
SERVER-45904 Create a standalone collection sharding state factory
- Closed
- is depended on by
-
SERVER-32198 Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"
- Closed
-
SERVER-46272 Make callers of keyBelongsToMe() to not go through collection metadata
- Closed
- is related to
-
SERVER-46679 Transaction test fails with Stale Shard Version error on 4.5
- Closed
- related to
-
SERVER-47268 noop_createIndexes_not_blocked_by_txn.js fails on snapshot errors within a transaction
- Closed
-
SERVER-47911 Prevent stale_mongos_and_restarted_shards_agree_on_shard_version.js from running in sharding_multiversion
- Closed