[SERVER-76485] movePrimary should set dbversion on recipient shard Created: 25/Apr/23  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Sprint: Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12
Participants:
Story Points: 1

 Description   

Currently, the movePrimary coordinator leaves the database version both on the donor and destination shard as UNKNOWN. Instead, we should make it so that before living the critical section, both donor and recipient have the correct db version installed in DSS.


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