[SERVER-44511] Make "hangInAwaitableIsMaster" failpoint in mongod Created: 08/Nov/19  Updated: 14/Dec/19  Resolved: 14/Dec/19

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

Type: New Feature Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Tess Avitabile (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-44509 Make isMaster wait for up to maxAwait... Closed
is depended on by SERVER-44814 Support "waitInIsMaster" failpoint on... Closed
Sprint: Repl 2019-12-16
Participants:

 Comments   
Comment by Tess Avitabile (Inactive) [ 14/Dec/19 ]

I will assume that this failpoint is sufficient for drivers and mongos testing. We will extend support for this failpoint to mongos inĀ SERVER-44814.

Comment by Tess Avitabile (Inactive) [ 09/Dec/19 ]

The server already has a failpoint waitInIsMaster. Unlike the proposed failpoint hangInAwaitableIsMaster, this will hang regardless of whether maxAwaitTimeMS and topologyVersion were specified. matt.broadstone, lamont.nelson, shane.harvey, is this sufficient for testing the client? If so, we will just add waitInIsMaster to the mongos implementation of isMaster.

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