[DOCS-4536] FSync+Lock does not work on WT Created: 16/Dec/14  Updated: 16/Jan/15  Resolved: 16/Jan/15

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.17, mongodb-3.0

Type: Task Priority: Major - P3
Reporter: Osmar Olivo Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-4652 Update fsync documentation to clarify... Closed
related to SERVER-16565 FsyncLock on WT should not imply "sna... Closed
Participants:
Days since reply: 9 years, 9 weeks, 1 day ago

 Description   

This has some implications in virtually every backup guide where fsyncLock is mentioned.

Most notably copying the data files using cp or taking filesystem snapshots when the journal is not on the same volume. We should think up what the new procedure should be and update the pages accordingly.

We should also determine if it is still unsafe to snapshot with no journal on the volume (or if it even is safe WITH a journal). If it is, I imagine we will just have to shutdown a secondary and stop writes to the system that way before taking the snapshot. But there may be a better way.


Generated at Thu Feb 08 07:48:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.