Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- PM-234-M3
- PM-234-T-autocommits

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19
Story Points:
2
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

SERVER-53910 Increment oplogEntriesFetched and oplogEntriesApplied in ReshardingOplogFetcher and ReshardingOplogApplier

Closed

is depended on by

SERVER-53912 ReshardingRecipientService instances to load metrics state upon instantiation

Closed

is duplicated by

SERVER-52774 Periodically persist metrics about resharding on shards

Closed

Assignee:: Lamont Nelson
Reporter:: Lamont Nelson
Participants:: Githook User, Lamont Nelson, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jan 20 2021 05:11:14 PM UTC
Updated:: Nov 06 2023 08:15:46 PM UTC
Resolved:: Apr 06 2021 08:54:32 PM UTC
Confidence Status Last Update:: 01/Mar/21 5:00 PM