[SERVER-16274] secondary fasserts trying to replicate an index Created: 21/Nov/14 Updated: 23/Mar/17 Resolved: 06/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.6.5, 2.8.0-rc0 |
| Fix Version/s: | 2.6.8, 2.8.0-rc5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||||||||||
| Steps To Reproduce: | Reproduction is not consistent, but it appears to happen during a sequence of index creations on the same collection (dropping the collection between each one), each with different options. One of the creations is in the background. You can see the name of the collection as well as the index name in the exception message in the ticket description. |
||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
A secondary fasserts with the following log message:
|
| Comments |
| Comment by Githook User [ 06/Feb/15 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by Githook User [ 06/Jan/15 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by Roy [ 21/Dec/14 ] |
|
Thanks Andy. |
| Comment by Andy Schwerin [ 20/Dec/14 ] |
|
mamoos1, the issue is marked "Backport Requested". Once a developer produces a fix on the master development branch, we will assess it for backport. |
| Comment by Roy [ 20/Dec/14 ] |
|
Hi, This actually happened to me with 2.6.6 as well. Thanks. |
| Comment by Eric Milkie [ 21/Nov/14 ] |
|
This is most likely related to the way we track background index builds on secondaries. |