-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
v5.0
-
Sharding 2021-05-17, Sharding 2021-05-31
-
1
As-is, the metrics component assumes control of starting/stopping duration tracking, and the timestamps are opaque to the surrounding system. For recovery, the resharding machines need direct access to the timestamps to durably persist them to metadata documents. To solve this, we will need to either:
- Change the metrics component so that starting/stopping tracking returns a timestamp, or
- Invert responsibility so that the resharding state machines generate timestamps then pass them into the metrics component.
- causes
-
SERVER-61473 Resharding coordinator calls ReshardingMetrics::onCompletion() multiple times on transient errors, leading to config server crash
- Closed