[SERVER-210] Manual write lock/unlock Created: 04/Aug/09 Updated: 29/May/12 Resolved: 25/Aug/09 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 0.9.7 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Carl Mercier | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
It would be great if we could manually write lock collections (ie: writes are buffered but not committed) and later manually unlock them. This is especially useful for backuping purposes. The database would still allow reads but writes would simply be delayed. I am looking to use this feature to perform an EBS snapshot on EC2, but fear taking a snapshot when the database is in an inconsistent state. MySQL has a similar feature. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 25/Aug/09 ] |
|
see |
| Comment by cmer [ 04/Aug/09 ] |
|
Such a feature would allow us to perform backups in a way similar to this: http://developer.amazonwebservices.com/connect/entry.jspa?categoryID=100&externalID=1663 |