determine storageEngine specificity in docs
(DOCS-4856)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Jason Zucchetto | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 8 years, 15 weeks, 6 days ago | ||||||||
| Description |
|
There are conflicting statements in the docs for backups regarding WiredTiger. This page references db.fsyncLock() and db.fsyncUnlock(): But when you dig further into db.fsyncLock for WiredTiger: "With WiredTiger the db.fsyncLock() and db.fsyncUnlock() operations cannot guarantee that the data files do not change. As a result, do not use these methods to ensure consistency for the purposes of creating backups." We should outline the exact procedure for a filesystem backup with WiredTiger, this is pretty heavily referenced in training/consulting. |
| Comments |
| Comment by Githook User [ 29/Oct/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message:
|