[SERVER-6499] compact's external sorter should use the default index version key comparator Created: 18/Jul/12 Updated: 11/Jul/16 Resolved: 25/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allen Gilbert | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
3.2.22-35.60.amzn1.x86_64, 7.5 GB RAM |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
I'm trying to compact one of my large, sharded collections. After setting up a new secondary with a copy of the master's data, the command failed when attempting to rebuild the index/shard key:
So, I re-copied the data and ran validate( {full: true}) first, which declared my collection to be healthy (ok's were all 1, no errors or invalidObjects). However, it failed again:
The stack trace from the secondary's log:
|
| Comments |
| Comment by auto [ 24/Jul/12 ] |
|
Author: {u'date': u'2012-07-24T16:04:13-07:00', u'email': u'aaron@10gen.com', u'name': u'Aaron'}Message: |
| Comment by auto [ 24/Jul/12 ] |
|
Author: {u'date': u'2012-07-23T14:43:40-07:00', u'email': u'aaron@10gen.com', u'name': u'Aaron'}Message: |
| Comment by auto [ 24/Jul/12 ] |
|
Author: {u'date': u'2012-07-23T13:10:55-07:00', u'email': u'aaron@10gen.com', u'name': u'Aaron'}Message: |