-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
0
To implement resharding oplog application support for capped collections, we skipped checking and working with the stash collections since capped collections are guaranteed to be on a single shard so they won't have duplicate _id's thus making stash collections redundant.
We should evaluate applying the same idea to sharded collections that exist only on a single shard or unsharded collections more broadly since it will make oplog application quicker.
- is related to
-
SERVER-89826 Investigate errors related to moving capped collection that are part of multi-document transactions
- Closed