[SERVER-5641] Mongodump against sharded system should lock collection during backup Created: 18/Apr/12 Updated: 14/Mar/17 Resolved: 02/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Tools |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | backup, distributed-lock, mongodump | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
The collections should be locked at the cluster level so no splits/migrates occur during the backup of that collection. This is probably best done with a new distlock-collection (with an implicit/explicit timeout) command issued between each getmore. |