-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
v4.9
-
-
Sharding 2021-05-03, Sharding 2021-05-17
-
2
I do not claim that this issue can cause actual production failures, but it was a real problem for me blocking from fully implementing SERVER-53950.
The idea I was trying to implement in SERVER-53950 was that we should always interrupt the primary service instance whenever we unregister it. One of the things that unregisters the service is the deletion of the state document.
However if I make this bridge as discussed in that bug, the resharding fails at the moment the state doc is deleted, before completion. I don't see a simple fix myself.
- is duplicated by
-
SERVER-52837 Gracefully shut down resharding state machines on stepdown/shutdown
- Closed
- related to
-
SERVER-60775 PrimaryOnlyService won't wait for prior Instance on step up if InstanceID had completed on an interceding primary already (ABA problem)
- Backlog
-
SERVER-57195 Convert resharding document deletion to use PersistentTaskStore instead of creating a WriteUnitOfWork
- Closed