-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 7.0.2, 7.1.0-rc3, 7.2.0-rc1
-
Component/s: None
-
Sharding EMEA
-
Fully Compatible
-
ALL
-
v7.2, v7.1, 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
When movePrimary fails during the clone phase due to any reason, the operation will be aborted and cleaned up on the next iteration.
During the movePrimary cleanup, the donor sends a drop for every collection that was expected to be cloned to the recipient shard. One of these collections could be <dbName>.system.views, which can't be dropped if there is any view bucket collection on the node. Therefore, if there is any sharded view collection on the recipient shard while <dbName>.system.views collection is being dropped, the movePrimary cleanup process will fail and the movePrimary will be retried forever.
- is depended on by
-
SERVER-78852 Test movePrimary and $out running concurrently
-
- Closed
-