[SERVER-10478] Very large documents can cause premature migration commit Created: 09/Aug/13 Updated: 11/Jul/16 Resolved: 12/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.6, 2.4.6, 2.5.2 |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Issue Status as of October 23rd, 2013 ISSUE SUMMARY USER IMPACT MongoDB v2.2 maintains a backup of every document involved in a chunk migration in a moveChunk directory (http://docs.mongodb.org/manual/faq/sharding/). It is possible to examine this directory programmatically to find documents migrated within the document size in question. MongoDB v2.4 has this option off by default. SOLUTION WORKAROUNDS If document loss is suspected, locate the moveChunk directory on the master replica of the donor shard at the time of the migration. The lost documents can be reinserted from that backup or your own regular backups. PATCHES |
| Comments |
| Comment by Dmitry Kireev [ 20/Aug/13 ] |
|
Thank you. For now we'll disable balancer. Thank you. |
| Comment by auto [ 12/Aug/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 12/Aug/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 12/Aug/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 10/Aug/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 09/Aug/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |