Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.0, v3.6
Sprint:
Repl 2018-11-05, Repl 2018-11-19, Repl 2018-12-03, Repl 2018-12-17, Repl 2019-01-14
Confidence Status:
None
Work Order:
3

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

Allow change streams to work with the speculative majority reads implementation, so that they can work correctly even without storage engine support for majority reads enabled.

depends on

SERVER-38218 AutoGetCollection doesn't need to call getPointInTimeReadTimestamp for non snapshot read concern levels

Closed

SERVER-37935 Remove read concern "majority" overrides for change streams test suites

Closed

is depended on by

SERVER-37221 Enable change streams with enableMajorityReadConcern:false

Closed

is related to

SERVER-34277 Add 'maxAwaitTimeMs' parameter to getMore command, deprecate usage of 'maxTimeMS' with getMore

Backlog

SERVER-38727 Add command parameter to specify max wait time for speculative majority reads

Closed

SERVER-38754 Add optimizations for change streams using speculative majority

Closed

related to

SERVER-57197 [ephemeralForTest] improve error message for change stream request

Closed

SERVER-37178 [POC] Allow change streams to work with "blocking" implementation of majority reads

Closed

(1 is related to, 2 related to)

Assignee:: Will Schultz
Reporter:: Will Schultz
Participants:: Githook User, Will Schultz
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Oct 10 2018 09:20:36 PM UTC
Updated:: Oct 29 2023 10:27:29 PM UTC
Resolved:: Dec 21 2018 09:54:52 PM UTC
Confidence Status Last Update:: 07/Nov/18 10:29 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates