[SERVER-68007] Clonning phase of the movePrimary cmd should specify a valid afterClusterTime Created: 13/Jul/22  Updated: 29/Oct/23  Resolved: 22/Jul/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-62206 Remove DBClientBase::query_DEPRECATED... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-07-25
Participants:
Linked BF Score: 33

 Description   

Another solution would be to clone always from the primary.



 Comments   
Comment by Githook User [ 22/Jul/22 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-68007 movePrimary should always clone data from the primary node
Branch: master
https://github.com/mongodb/mongo/commit/f98b3361fbab4e02683325cc0e6ebaa69d6af1df

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