[SERVER-53820] Test recipient secondaries can recover any necessary state after initial sync completes Created: 14/Jan/21  Updated: 29/Oct/23  Resolved: 07/Jun/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc2, 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Vishnu Kaushik
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-E, pm-1791_non-cloud-blocking
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Repl 2021-05-17, Repl 2021-05-31, Repl 2021-06-14
Participants:

 Description   

At each point in the recipient's migration, the recipient secondaries can recover any necessary state after initial sync completes

  • Before data clone begins
  • During data clone
  • During oplog application


 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 10/Jun/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-53820 Test recipient secondaries can recover any necessary state after initial sync completes
Branch: v5.0
https://github.com/mongodb/mongo/commit/6b6035aa6cdcb56965abbf215fc9085afe494114

Comment by Githook User [ 07/Jun/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-53820 Test recipient secondaries can recover any necessary state after initial sync completes
Branch: master
https://github.com/mongodb/mongo/commit/a830486be77aa46e533d7ea9287b06f60b41e9bc

Comment by Vishnu Kaushik [ 03/Jun/21 ]

SERVER-57399 has been filed since the third case ("during oplog application") currently fails.

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