[SERVER-44952] Implement awaitable isMaster client protocol without exhaustAllowed Created: 04/Dec/19  Updated: 27/Oct/23  Resolved: 20/Feb/20

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Janna Golden
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-43332 Replace RSM implementation with SDAM-... Closed
depends on SERVER-44950 Update SDAM with topologyVersion fiel... Closed
is depended on by SERVER-44954 Use tailable awaitable isMaster Closed
Related
is related to SERVER-44510 Service layer / command changes to im... Closed
Sprint: Service Arch 2020-01-27, Service Arch 2020-02-10, Service Arch 2020-02-24
Participants:

 Description   

Awaitable isMaster can be triggered via the use of topologyVersion and maxAwaitTimeMS fields. We should begin to use these isMasters with the ReplicaSetMonitor scanning. This does not require use of exhaust/tailable cursors.

The use of awaitable isMaster may need to be opt-in for testing until we have mongodden/mongossen that support this work. However, this work should be verified for correctness via modification of existing integration tests and js test suites.


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