-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2026-09-14
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
If the MovePrimary restarts because of a stepdown (so the phase is not unset) then in the next run it checks again if the target node is draining. If during the stepdown the target started to drain, the check fails, but since the mustAlwaysMakeProgress is very weak here, it retries infinitely.
Meanwile the removeShard cannot finish as it's waiting for the coordinators to finish, so never will let the draining go away.
This causes a deadlock.
- is duplicated by
-
SERVER-134349 Concurrent movePrimary and startShardDraining/removeShard can cause movePrimary to hang
-
- Closed
-