[SERVER-17557] Display warning when running db.fsyncLock() when running with WiredTiger Created: 12/Mar/15  Updated: 15/Sep/15  Resolved: 15/Sep/15

Status: Closed
Project: Core Server
Component/s: Storage, Usability
Affects Version/s: 3.0.0
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Ian Daniel Assignee: Daniel Pasette (Inactive)
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-18899 Enable fsyncLock on WiredTiger to all... Closed
Related
is related to DOCS-4751 Document that backing up a mongod run... Closed
is related to SERVER-16565 FsyncLock on WT should not imply "sna... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Building on SERVER-16565, please consider displaying a warning message when db.fsyncLock() is run when WiredTiger is running, stating that fsyncLock is not supported for backups with WiredTiger.

The messaging would be along the lines of the text we added to the product documentation in DOCS-4751, namely:

With WiredTiger, the db.fsyncLock() command cannot guarantee that the data files do not change. As a result, do not use this method to ensure consistency for the purposes of creating backups.



 Comments   
Comment by Daniel Pasette (Inactive) [ 15/Sep/15 ]

This is obviated by SERVER-18899, which will be resolved in 3.1.9.

Comment by Daniel Pasette (Inactive) [ 11/Jun/15 ]

This may go away as we're planning to enable fsyncLock on WiredTiger.

Generated at Thu Feb 08 03:44:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.