-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
With the changes from track unsharded collections, the test agg_out.js fails when random migration failpoints are enabled. The test reports LockBusy error status. Below, there is an example of the output.
[[https://parsley.mongodb.com/test/mongodb_mongo_master_enterprise_amazon_linux2_arm64_all_feature_flags_concurrency_sharded_causal_consistency_and_balancer_4_linux_enterprise_patch_dbb9c9d1ace105003f844286b299c1c63fd807ef_65ca6904e3c331e96412d9af_24_02_12_18_54_17/0/bfe8f70b125c3c0450b638cc52ea0e51?bookmarks=0,897&shareLine=0|Log example]]
- depends on
-
SERVER-85441 Extend `balancerShouldReturnRandomMigrations` failpoint to additionally move random unsharded collections
- Closed
- duplicates
-
SERVER-86802 Re-enable agg_out.js FSM test in suites with random balancing
- Closed