[SERVER-21483] Secondary can reorder capped collection inserts with document-level locking Created: 16/Nov/15 Updated: 03/Dec/15 Resolved: 20/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.7 |
| Fix Version/s: | 3.0.8, 3.2.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Sprint: | QuInt C (11/23/15) | ||||||||
| Participants: | |||||||||
| Description |
|
In fillWriterVectors() we distribute inserts to threads based on a hash of the _id and namespace. This means that inserts to capped collections can happen in a different order than the primary. |
| Comments |
| Comment by Githook User [ 03/Dec/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'redbeard0531@gmail.com'}Message: Manual backport of bbff16c4b196133718b3d3f5cf7ce2095cc6d2b9 |
| Comment by Githook User [ 20/Nov/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |