[SERVER-12662] Two background index builds in parallel with unique key constraint violations crashes secondary Created: 09/Feb/14 Updated: 11/Jul/16 Resolved: 15/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.4.9 |
| Fix Version/s: | 2.4.10 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
| Comments |
| Comment by Githook User [ 14/Mar/14 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Githook User [ 14/Mar/14 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Amalia Hawkins [ 13/Mar/14 ] |
|
Attached is a js script which replicates the problem. |
| Comment by Githook User [ 13/Feb/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: Revert " This reverts commit 2f3bd6fc8f3b50bf4802f4477c55660355cff9fe. |
| Comment by Eric Milkie [ 13/Feb/14 ] |
|
Adding an _id index explicitly (on a collection that didn't have one already) doesn't work. Will fix this. |
| Comment by Githook User [ 12/Feb/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by Eric Milkie [ 12/Feb/14 ] |
|
I diagnosed the issue and have a proposed fix for 2.4 branch. For now I am targeting this only at 2.4.10. The issue is that if the index already exists, we still log the index-create in the oplog. In 2.6.0rc0 this behavior is changed such that nothing is logged if the index already exists. |