-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Fully Compatible
-
Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19
-
2
Only the oplog applier metrics need to be tracked specially. The others are tracked on per-collection basis.
oplog applier:
https://github.com/mongodb/mongo/blob/06b4a33530bfd58fab55e1fdda506b51f75f1ec5/src/mongo/db/s/resharding/resharding_oplog_applier.h#L56
current progress update code:
https://github.com/mongodb/mongo/blob/6308db5c83a3e95f4532c63df8b635b8090036ae/src/mongo/db/s/resharding/resharding_oplog_applier.cpp#L470
- causes
-
SERVER-82838 ReshardingOplogApplier uses {w: "majority", wtimeout: 60000} write concern when persisting resharding oplog application progress
-
- Closed
-
- depends on
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is duplicated by
-
SERVER-52774 Periodically persist metrics about resharding on shards
-
- Closed
-