Loading...

XML

Word

Printable

JSON

Type: New Feature
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, Repl 2019-12-16, Repl 2019-12-30
Confidence Status:
None
Work Order:
3

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

See design for details. We do not need to ensure that if the server detects a client disconnect while waiting to send a reply, the server cleans up connection resources, since that will be done in ~~SERVER-44523~~. Leave exhaust cursors as a special case to be refactored later.

Log at log level 3 whether exhaust is used.

depends on

SERVER-44509 Make isMaster wait for up to maxAwaitTimeMS

Closed

is depended on by

SERVER-44517 Refactor exhaust cursors on top of exhaust isMaster code changes

Closed

SERVER-44521 Implement exhaust isMaster for mongos

Closed

SERVER-44707 Store commit point at which the last batch was returned in ClientCursor and use that as the lastKnownCommittedOpTime for the next synthetic getMore

Closed

SERVER-44523 Cease streaming exhaust isMaster replies on error (mongod)

Closed

SERVER-44954 Use tailable awaitable isMaster

Closed

related to

SERVER-44952 Implement awaitable isMaster client protocol without exhaustAllowed

Closed

(1 is depended on by, 1 related to)

Assignee:: Tess Avitabile (Inactive)
Reporter:: A. Jesse Jiryu Davis
Participants:: A. Jesse Jiryu Davis, Githook User, Haley Connelly, Lingzhi Deng, Matthew Russotto, Mira Carey, Tess Avitabile
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Nov 08 2019 07:43:48 PM UTC
Updated:: Jan 08 2024 03:22:54 PM UTC
Resolved:: Dec 16 2019 09:32:13 PM UTC
Confidence Status Last Update:: 02/Dec/19 4:37 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates