[SERVER-32637] Ensure that upgrading to 3.6 when on pv0 doesn't break if you don't explicitly turn off readConcernMajority - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.6.3
Component/s: Replication, Storage
Labels:
None

Backwards Compatibility:
Minor Change
Operating System:
ALL
Backport Requested:

v3.6
Sprint:
Storage 2018-01-15, Storage 2018-01-29
Case:

Description

In 3.6, readConcernMajority support is enabled by default, but having readConcernMajority support enabled while running in replication protocolVersion 0 causes problems. We should ensure that the upgrade to 3.6 works as expected even if using pv0.

Attachments

Issue Links

is related to

SERVER-35941 Don't maintain full stable optime candidate list on secondaries in PV0

Closed

Activity

People

Assignee:: Eric Milkie

Reporter:: Spencer Brody (Inactive)

Participants:: Davis Ford, Eric Milkie, Githook User, Spencer Brody

Votes:: 1 Vote for this issue

Watchers:: 11 Start watching this issue

Dates

Created:: Jan 10 2018 07:36:38 PM UTC

Updated:: Jul 02 2018 06:35:20 PM UTC

Resolved:: Jan 29 2018 04:32:20 PM UTC