[DOCS-2303] Comment on: "manual/reference/command/fsync.txt" Created: 26/Nov/13 Updated: 03/Nov/17 Resolved: 26/Nov/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Zhong Liang Ong | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 13.04 Server 64-bit, MongoDB 2.4.6 3-member replica set (1 primary, 2 secondary) Location: http://docs.mongodb.org/manual/reference/command/fsync/ |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 10 years, 12 weeks, 1 day ago | ||||||||
| Description |
|
It was unclear whether the fsync command takes effect on replica sets. Is this thread still valid? https://groups.google.com/d/msg/nosql-databases/qbUnbtJcBRY/MET9SCPrdXkJ |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 26/Nov/13 ] |
|
The fsync command (the linked page) reflects a method used to flush pending writes to disk and lock the instance from future writes for the purpose of completing a backup. The linked thread relates to a property of the getLastError command (http://docs.mongodb.org/manual/reference/command/getLastError/). See the following page for more information: http://docs.mongodb.org/v2.4/core/write-concern/#journaled |