Loading...

XML

Word

Printable

JSON

Details

Type: Task
Resolution: Gone away
Priority: Major - P3
Fix Version/s: 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113
Affects Version/s: None
Component/s: manual, Server
Labels:
None

Epic Link:
DOCSP-15042

Description

Description

Downstream Change Summary

The "newlyAdded" field present in on-disk Replica Set Configs in 4.6 will not be accepted in any reconfig, force or non-force.

Description of Linked Ticket

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

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)

Here is the Technical Design that specifies the behavior around the newlyAdded fields

Attachments

Issue Links

documents

SERVER-47495 Ban force reconfig with "newlyAdded" fields

Closed

is duplicated by

DOCS-13582 Investigate changes in SERVER-47331: Rethink the transition from force reconfig to safe reconfig

Closed

Activity

People

Assignee:: Joseph Dougherty

Reporter:: Backlog - Core Eng Program Management Team

Participants:: Backlog - Core Eng Program Management Team, Jeffrey Allen, Joseph Dougherty, Judah Schvimer

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: May 14 2020 08:00:02 PM UTC

Updated:: Nov 13 2023 06:05:11 PM UTC

Resolved:: Aug 17 2021 07:53:58 PM UTC

Days since reply:: 2 years, 15 weeks, 1 day ago