[SERVER-56670] Ensure reconfig cannot roll back committed writes in replica sets with multiple arbiters Created: 05/May/21  Updated: 06/Dec/22  Resolved: 14/Oct/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Xuerui Fa Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-55376 Reconfig can roll back committed writ... Closed
is depended on by MONGOSH-891 Add check for PSA set in reconfigForP... Open
Related
related to SERVER-56481 Update TLA+ spec for reconfig to mode... Open
related to DOCS-14937 [SERVER] Document that we no longer s... Closed
related to SERVER-60696 Add a server parameter to disallow mu... Closed
Assigned Teams:
Replication
Operating System: ALL
Sprint: Repl 2021-08-09, Repl 2021-08-23, Repl 2021-09-06
Participants:

 Description   

In SERVER-55376, we resolved a bug where reconfig to a PSA set could lead to committed writes being rolled back. However, since users are able to configure their replica sets to have more than one arbiter, we may need to extend our solution in SERVER-55376 to catch these cases.


Generated at Thu Feb 08 05:39:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.