[SERVER-41341] sharded_backup_restore.js should not drop minvalid collection Created: 28/May/19  Updated: 29/Oct/23  Resolved: 29/May/19

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

Type: Bug Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-06-03
Participants:

 Description   

In the hot backup documentation, minvalid collection is dropped as part of the restore process. However, it needs to be kept to pass this check on startup. The sharded_bakcup_restore.js test worked because I mistakenly dropped 'minValid' rather than 'minvalid' collection.



 Comments   
Comment by Githook User [ 29/May/19 ]

Author:

{'email': 'xiangyu.yao@mongodb.com', 'name': 'Xiangyu Yao', 'username': 'xy24'}

Message: SERVER-41341 sharded_backup_restore.js should not drop minvalid collection
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/dcca6340e399b50f624c9569a6daaf5fcb7a13ec

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