[SERVER-21646] Inserts and updates to replicated capped collections must be single threaded Created: 24/Nov/15 Updated: 03/Dec/15 Resolved: 01/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.2.0-rc4 |
| Fix Version/s: | 3.0.8, 3.2.0-rc5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rui Zhang (Inactive) | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | sys-perf-reg | ||
| 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 D (12/14/15) | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Similar to Additionally we need to do this with inserts for correctness to ensure that the order of the capped collection matches the order of the insert entrees in the oplog. Original title and description: with insert_capped test, secondary cannot keep up with primary. This is introduced somewhere between c76b4ff to 0730c65,
|
| Comments |
| Comment by Githook User [ 03/Dec/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This prevents the primary from running significantly faster than secondaries. (cherry picked from commit f45b7c8e34743ba89407d90ee3392acb0d2be255) |
| Comment by Mathias Stearn [ 01/Dec/15 ] |
| Comment by Githook User [ 01/Dec/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This prevents the primary from running significantly faster than secondaries. |
| Comment by Daniel Pasette (Inactive) [ 24/Nov/15 ] |
|
I am easily able to repro the issue on: |
| Comment by Daniel Pasette (Inactive) [ 24/Nov/15 ] |
|
Can you show exactly how you set up the machines? What's the size of the oplog? |