[SERVER-16026] Documents with secondary unique indexed fields may not replicate properly on KV storage engines Created: 07/Nov/14 Updated: 11/Jul/16 Resolved: 10/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Replication |
| Affects Version/s: | 2.7.8 |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
When replicating document ops with doc-level-locking storage engines, we may batch apply operations in parallel within the same collection. If unique secondary indexes exist (that is, unique indexes other than id), their unique constraints may be temporarily violated during the application of a batch of ops. If this happens, the secondary node would detect this and shut down before data corruption resulted. |
| Comments |
| Comment by Githook User [ 10/Nov/14 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: |
| Comment by Githook User [ 10/Nov/14 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |