[SERVER-30280] WTKVEngine::beginBackup should check `_ephemeral` before creating a backup cursor. Created: 24/Jul/17  Updated: 30/Oct/23  Resolved: 02/Aug/17

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2017-08-21
Participants:
Linked BF Score: 0

 Description   

An ephemeral WT can no longer create a backup cursor. This breaks the `fsync` and lock command which is used for more than just taking a filesystem copy.



 Comments   
Comment by Githook User [ 10/Aug/17 ]

Author:

{'name': 'Maria van Keulen', 'email': 'maria@mongodb.com'}

Message: SERVER-30280 Don't create a backup cursor if storageEngine is inMemory
Branch: master
https://github.com/mongodb/mongo/commit/3564173cb49ad2979281f4a1a067e841e8a2384d

Comment by Maria van Keulen [ 07/Aug/17 ]

Not sure why the Githook User didn't post this but here is the commit:
https://github.com/mongodb/mongo/commit/3564173cb49ad2979281f4a1a067e841e8a2384d

Comment by Daniel Pasette (Inactive) [ 31/Jul/17 ]

this seems to be racking up a lot of failures quickly. can we bump priority?

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