[SERVER-73890] Only run the resilient movePrimary in random_DDL_operations.js FSM Created: 10/Feb/23  Updated: 29/Oct/23  Resolved: 13/Feb/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 6.3.0-rc1

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: PM-2144-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.3
Sprint: Sharding EMEA 2023-02-20
Participants:
Linked BF Score: 136

 Description   

The resilient version of the movePrimary is enabled by default starting from version 7.0, and this guarantees the correctness of the cached database version on both donor and recipient shards

The random_DDL_operations.js FSM also runs in multiversion suites (specifically, concurrency_sharded_replication_last_continuous_new_old_old_new and concurrency_sharded_replication_last_lts_new_old_old_new), and this implies that the old and non-resilient version of the movePrimary could run.

The goal of this ticket is to restrict the execution of the movePrimary state to when the ResilientMovePrimary feature flag is enabled.



 Comments   
Comment by Githook User [ 13/Feb/23 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-73890 Only run the resilient movePrimary in random_DDL_operations.js FSM
Branch: v6.3
https://github.com/mongodb/mongo/commit/b5f7f35d46dab278abac976afe48ebf9632572b1

Comment by Githook User [ 13/Feb/23 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-73890 Only run the resilient movePrimary in random_DDL_operations.js FSM
Branch: master
https://github.com/mongodb/mongo/commit/e0a060e8d1f753c649a68759e0b2a02076efaab5

Generated at Thu Feb 08 06:25:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.