Details
-
Task
-
Status: Open
-
Major - P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10, Sharding EMEA 2022-05-30
Description
The random migration failpoints have possible exposed various failures and will be disabled until we investigate the BFs that were encountered. Once we have resolved these issues, the failpoint should be reenabled.
Attachments
Issue Links
- depends on
-
SERVER-43106 Test create_index_background_wildcard.js doesn't account for orphans when run with random migrations
-
- Closed
-
-
SERVER-43196 Blacklist update_where.js from sharded concurrency suites with balancer on and no txn override
-
- Closed
-
-
SERVER-61742 Balancer may trip invariants due to concurrent usage of opCtx from different threads
-
- Closed
-
-
SERVER-61769 Attempting to run an aggregation with $out or $merge in a transaction on a sharded cluster leaves idle cursors open
-
- Closed
-
-
SERVER-62710 AsyncRequestsMerger won't attempt to cleanup shard cursors when deadline is exceeded
-
- Closed
-
-
SERVER-42914 Implement random chunk selection policy for balancer for use in concurrency_*_with_balancer workloads
-
- Closed
-
-
SERVER-61759 Unsetting the AllowMigrations flag should abort ongoing migrations
-
- Closed
-
-
SERVER-61810 rename_sharded_collection.js workload needs to retry split command
-
- Closed
-
-
SERVER-61811 Do not run indexed_insert_where.js on concurrency_sharded_causal_consistency_and_balancer
-
- Closed
-
-
SERVER-61835 Fix how SBE plan cache deals with ShardFilterer
-
- Closed
-
-
SERVER-61840 create_index_background_partial_filter.js and create_index_background_wildcard.js should not run on _with_balancer suites
-
- Closed
-