[SERVER-255] add optional write lock to fsync command Created: 25/Aug/09 Updated: 12/Jul/16 Resolved: 02/Jan/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
force an full disk sync, and then optionally lock the db for writes until a manual unlock See |
| Comments |
| Comment by Dwight Merriman [ 02/Jan/10 ] |
|
http://www.mongodb.org/display/DOCS/Snapshotting+and+the+fsync+Command |
| Comment by auto [ 02/Jan/10 ] |
|
Author: {'name': 'unknown', 'email': 'Administrator@.(none)'}Message: |
| Comment by auto [ 11/Nov/09 ] |
|
Author: {'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: fsync command part of |
| Comment by Eliot Horowitz (Inactive) [ 11/Nov/09 ] |
|
added the fsync command, just need to add a lock option |
| Comment by cmer [ 21/Sep/09 ] |
|
I am THRILLED that you decided to move this to 1.2. I'm sure many of us will also be! Thanks for caring! |
| Comment by cmer [ 10/Sep/09 ] |
|
Running a 64 bit slave just for backup purposes on EC2 is ~$350/mo. Pretty expensive for backups! |
| Comment by James Golick [ 10/Sep/09 ] |
|
This would be huge for those of us running Mongo on ec2. Backing up with EBS snapshots is ridiculously convenient. |
| Comment by cmer [ 10/Sep/09 ] |
|
Would be great to see this implemented before 1.3.0. It would REALLY help in production. Just saying... |
| Comment by Erwan Arzur [ 10/Sep/09 ] |
|
We have discussed this issue on the group and would really like to see something like this implemented. Thanks ! |