Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.3
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2019-12-02
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

This will eventually use the ReplicationCoordinator to know about topology changes, but not yet.

Simulate an isMaster request with or without topologyVersion and with or without maxAwaitTimeMS. Assert the server follows the rules in the main design doc.

Log at log level 3 whether maxAwaitTimeMS is used.

depends on

SERVER-44508 Add maxAwaitTimeMS and topologyVersion to isMaster command

Closed

is depended on by

SERVER-44510 Service layer / command changes to implement exhaust isMaster

Closed

SERVER-44511 Make "hangInAwaitableIsMaster" failpoint in mongod

Closed

SERVER-44514 TopologyCoordinator::awaitTopologyChanges returns early on primary topology changes

Closed

SERVER-44813 Implement isMaster with maxAwaitTimeMS and topologyVersion on a standalone

Closed

Assignee:: Haley Connelly
Reporter:: A. Jesse Jiryu Davis
Participants:: A. Jesse Jiryu Davis, Githook User, Haley Connelly
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Nov 08 2019 07:40:54 PM UTC
Updated:: Oct 29 2023 10:15:11 PM UTC
Resolved:: Nov 25 2019 10:39:52 PM UTC
Confidence Status Last Update:: 18/Nov/19 10:48 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates