-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Programmability
-
Fully Compatible
-
ALL
-
Workload Resilience 2025-12-08
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We added new server status metrics as part of SERVER-110000 but it seems to cause issues with ftdc files when resharding occurs since it can change the structure of the server status object.
We think one of the solutions could fix the issue:
- Apply a strict order on the shards in the server status object
- Track the creation and removal order to keep the structure of the object consistent over time
- is related to
-
SERVER-110000 Implement new server status metrics for Shard::RetryStrategy
-
- Closed
-