Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2023-03-06, Repl 2023-03-20
Confidence Status:
None
Work Order:
3

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

The current WaitForMajorityService is waiting for a majority write concern, not a majority read concern. This only works on primaries and returns an error on step down. For some tasks we actually want to wait on read concern instead, and it make sense for these to be provided by the same service.

has to be done before

SERVER-74555 Re-introduce majority commit point advancement notification mechanism and use for change streams

Closed

SERVER-74754 Clean up uses of WaitForMajorityService::waitForMajority

Closed

Assignee:: Matthew Russotto
Reporter:: Matthew Russotto
Participants:: Githook User, Matthew Russotto
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Mar 03 2023 05:34:56 PM UTC
Updated:: Oct 29 2023 09:25:19 PM UTC
Resolved:: Mar 13 2023 04:14:18 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates