[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: |
|
||||||||||||
| 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Ā |
| 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. |