SERVER-80135 make shards refresh asynchronously the collection metadata after a shardCollection. In drop_collection_if_uuid_not_matching.js a direct connection to the shard is established and after a shardCollection an insert command is executed, which races with the refresh. If the insert wins, then the test will fail with a StaleConfig error.
We could fix this by making the test to wait for the refresh to happen, or force a refresh after the shardCollection.
- is caused by
-
SERVER-80135 Allow ShardCollection to work correctly when an unsharded collection is not located on the DBPrimary
- Closed
- is related to
-
SERVER-88753 restart_transaction.js should not assume the filtering information is known after a createCollection command
- Closed