-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
0
If the analyzeShardKey command is executed on a unique shard key and an unclean shutdown takes place, the metrics returned by the command can be incorrect (as seen in BF-30851 and BF-35231). This is because the analyzeShardKey metrics rely on the $storageStats.count returned by $collStats. We must define the expectation of the metrics returned in such scenarios. As a fix for the two BFs linked, we removed the checking of the metrics returned.