[SERVER-50982] PrimaryOnlyService::lookupInstance should take an OperationContext and use interruptible waits Created: 16/Sep/20  Updated: 29/Oct/23  Resolved: 23/Sep/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
Related
related to SERVER-51650 Primary-Only Service's _rebuildCV sho... Closed
related to SERVER-50937 Make resharding coordinator support r... Closed
related to SERVER-51518 Reconcile how PrimaryOnlyService::loo... Closed
is related to SERVER-51096 PrimaryOnlyService::getOrCreateInstan... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service arch 2020-10-05
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 23/Sep/20 ]

Author:

{'name': 'Spencer T Brody', 'email': 'spencer@mongodb.com', 'username': 'stbrody'}

Message: SERVER-50982 Fix race condition in PrimaryOnlyServiceTest::LookupInstanceInterruptible
Branch: master
https://github.com/mongodb/mongo/commit/62e89bd2119904531b591b6948f57b00eb52ec79

Comment by Githook User [ 23/Sep/20 ]

Author:

{'name': 'Spencer T Brody', 'email': 'spencer@mongodb.com', 'username': 'stbrody'}

Message: SERVER-50982 Use interruptible wait in PrimaryOnlyService::lookupInstance
Branch: master
https://github.com/mongodb/mongo/commit/3d6a6a1dce2a4c3bb802d7f004b106f36ccd283b

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