Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.4
Affects Version/s: None
Component/s: Replication
Labels:
- safe-reconfig-cmd

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2020-02-10, Repl 2020-02-24, Repl 2020-03-09
Linked BF Score:
28
Confidence Status:
None
Work Order:
3

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

Oplog Commitment condition checks all committed entries in the previous config C_i-1 are also committed in the current config C_i.

Skip oplog commitment check on force reconfig.

is related to

SERVER-46473 Config replication and oplog commitment checks must only count voting nodes towards majority

Closed

SERVER-46522 Config oplog commitment wait must retrieve optime under replication mutex

Closed

related to

SERVER-45086 Record the last committed optime in the previous config on reconfig

Closed

SERVER-46894 Wait for the current config to be committed before running reconfig

Closed

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

Created:: Dec 12 2019 05:38:14 AM UTC
Updated:: Oct 29 2023 10:14:09 PM UTC
Resolved:: Feb 26 2020 04:40:42 AM UTC
Confidence Status Last Update:: 31/Jan/20 7:06 PM