This createCollection command can abort the transaction and throw StaleConfig if the CollectionMetadata is unknown, which is guaranteed by this point. Most of the time, it doesn't throw because mongoS retries transparently as it's the first statement in the transaction, but that requires `otherDb`'s primary shard to be different from `dbName`'s, otherwise it would be the second statement in the transaction (the first being this dummy operation).
Prevent StaleConfig error in placement_conflict_time.js
- Assignee:
-
Aitor Esteve Alvarado
- Reporter:
-
Aitor Esteve Alvarado
- Votes:
-
0 Vote for this issue - Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: