[SERVER-50919] Make sure PrimaryOnlyService Instance completion Futures resolve if the instance is interrupted due to stepdown or shutdown Created: 14/Sep/20  Updated: 15/Sep/20  Resolved: 15/Sep/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-50926 Don't hold onto a shared_ptr to Insta... Closed
related to SERVER-50953 Remove completionFuture from PrimaryO... Closed
Operating System: ALL
Sprint: Service arch 2020-09-21
Participants:

 Comments   
Comment by Spencer Brody (Inactive) [ 15/Sep/20 ]

This already works properly for stepdown. For shutdown it is possible to have a case where this future never resolves, but if everyone waiting on that future is using an interruptible wait, they would be interrupted by the shutdown process. So this seems pretty low priority and unlikely to cause real issues. SERVER-50953 would also allow us to solve this issue by managing the lifetime of the completionFuture the same way that Instances manage the lifetime of all their other futures.

Generated at Thu Feb 08 05:24:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.