-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
ClusterScalability 9Nov-23Nov
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
safe_secondary_reads_causal_consistency.js, when authoritative shards are enabled, waits for hangBeforePostMigrationCommitRefresh to indicate that we've committed to the config server. However, this failpoint lives in the MigrationSourceManager, which may not exist if a failover occurs. Instead, it should use hangInMoveRangeCoordinatorShardCatalogCommit, which always fires after we've committed to the config server.