[SERVER-6635] mongodump --repair does not stop at extent boundaries Created: 28/Jul/12 Updated: 11/Jul/16 Resolved: 29/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.2.0-rc0 |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Daniel Pasette (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
When running mongodump with the --repair option, the intent is to traverse each document in each extent for a collection, starting both at the first extent and traversing forward, then from the last extent and traversing backwards. The current implementation doesn't stop at extent boundaries and writes out all documents after the end of the current extent, then repeats this for the next extent, and so on. It does the same thing for the backwards pass. This causes the dumped file to be much larger than the original collection and overruns 100% in the progress meter. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 19/Mar/13 ] |
|
given how late this is, I don't know that it's useful given that we're not maintaining 2.0 documentation explicitly, it might just confuse things in the 2.2 branch... |
| Comment by auto [ 29/Jul/12 ] |
|
Author: {u'date': u'2012-07-29T07:54:17-07:00', u'email': u'dan@10gen.com', u'name': u'Dan Pasette'}Message: |
| Comment by auto [ 29/Jul/12 ] |
|
Author: {u'date': u'2012-07-29T07:47:39-07:00', u'email': u'dan@10gen.com', u'name': u'Dan Pasette'}Message: |
| Comment by auto [ 29/Jul/12 ] |
|
Author: {u'date': u'2012-07-28T14:22:52-07:00', u'email': u'dan@10gen.com', u'name': u'Dan Pasette'}Message: |