[SERVER-16640] Long running queries on the secondary with WT Created: 22/Dec/14 Updated: 15/Jan/15 Resolved: 29/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
We have disabled yielding with WT, because it is not necessary due to the use of snapshots. On secondaries though, because of the way the Parallel Batch Writer lock is implemented, it is possible that a long running query would prevent the log applier threads from starting until it is completed and thus cause backlog. This ticket is to verify this behaviour and if it turns out to be true to figure out a solution. |
| Comments |
| Comment by Kaloian Manassiev [ 29/Dec/14 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Andy Schwerin [ 24/Dec/14 ] |
|
Lack of yielding helped expose |