-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 6.3.0, 7.0.0, 7.1.0, 7.3.0-rc0, 7.2.0-rc3
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
v7.2, v7.0
-
Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The test performs the following operation
- create an invalid index
- drop the invalid index
- run validateDbMetadata and check no errors are returned
However, due to migrations the following might happen:
- Drop starts
- Migration from shard0 to shard1 starts
- Migration starts creation of index on shard1
- Drop index drops on shard0 but not shard1 (not committed yet)
- Migration now commits the create index on shard1
in this case, we have left an invalid index on shard1, which will make the test failing. The test should stay black-listed until PM-2077 is completed which should solve the known issue.
- is caused by
-
SERVER-43099 Reenable random chunk migration failpoint for concurrency with_balancer suites
-
- Closed
-