Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2020-05-04, Repl 2020-05-18
Confidence Status:
None

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

This is the outcome of the discussion in ~~SERVER-47331~~.

is related to

SERVER-46347 Ensure that force reconfigs are not given a 'newlyAdded' field

Closed

SERVER-46348 Test behavior when a user provides a 'newlyAdded' field in a force-reconfig

Closed

SERVER-46350 Test that force reconfig removes a 'newlyAdded' field if one exists but is not provided in the reconfig

Closed

SERVER-46352 Ensure the 'newlyAdded' field is always true when present, even for force-reconfigs

Closed

SERVER-47331 Rethink the transition from force reconfig to safe reconfig

Closed

Assignee:: Judah Schvimer

Reporter:: Judah Schvimer

Participants:: Githook User, Judah Schvimer, Tess Avitabile

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: Apr 13 2020 12:49:34 PM UTC

Updated:: Oct 29 2023 10:09:36 PM UTC

Resolved:: May 14 2020 08:00:01 PM UTC

Confidence Status Last Update:: 04/May/20 8:14 PM