[SERVER-61344] Make sure cloning is complete before killing the backup cursor Created: 09/Nov/21  Updated: 29/Oct/23  Resolved: 17/Nov/21

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

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

Issue Links:
Related
is related to SERVER-61343 Invariant when killing backup cursor Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Replication 2021-11-29
Participants:

 Description   

Currently, killing the backup cursor while still copying the file results in an invariant. This is a separate bug, but it makes sense to stop copying before killing the backup cursor anyway.



 Comments   
Comment by Githook User [ 17/Nov/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: SERVER-61344 Make sure cloning is complete before killing the backup cursor
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/154c5fdcda16041dfab92ef92f2f1bccfa02c8b1

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