[SERVER-13336] Count with no results, never yields Created: 24/Mar/14 Updated: 11/Jul/16 Resolved: 25/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Querying |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | 2.6.0-rc3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | hari.khalsa@10gen.com |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
This commit causes a regression such that no yielding will happen if the policy isn't set due to never entering the loop, which enables the auto-yielding policy. This can also be seen in more complicated scenarios where the timer has yet to trigger the policy and nothing is returned thus delaying the policy being set until a result is found (after the timer triggers), and then yielding will happen after that. The easiest way to see this is to run a count with a query which matches nothing, causing a collection scan. This also affects maxTimeMS timeouts, and trying to kill the op, since without the yielding checks the count cannot be terminated. |
| Comments |
| Comment by Githook User [ 30/Mar/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Now that counts can yield, they can be killed. The killAll() calls above were (cherry picked from commit 00c8264c88edbbda91c375063c2c612b1db18702) |
| Comment by Githook User [ 30/Mar/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Now that counts can yield, they can be killed. The killAll() calls above were |
| Comment by Githook User [ 25/Mar/14 ] |
|
Author: {u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}Message: Revert " This reverts commit 2850cc7253344c639bc9a01bc6dff3ffd2cca422. |
| Comment by Githook User [ 25/Mar/14 ] |
|
Author: {u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}Message: Revert " This reverts commit 2850cc7253344c639bc9a01bc6dff3ffd2cca422. |