-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.4.17
-
Component/s: Internal Code
-
Fully Compatible
-
ALL
-
Sharding 2018-10-22
-
1
The Notification::waitFor call is not interruptible in the 3.4 branch and this could potentially cause deadlock at config server stepdown followed immediately by step-up, due to its usage in the sharding Balancer code. While the chance for such a deadlock is extremely rare, making Notification::waitFor interruptible should be very safe to include in 3.4.
We can just pick-up the changes to notification.h from this change.
- backports
-
SERVER-25062 Implement interruptible sleep and condition variable waitFor methods on OperationContext
- Closed