[SERVER-24511] Make frequency with which background job that kills timed-out cursors is run configurable Created: 09/Jun/16 Updated: 19/Jul/16 Resolved: 14/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.10 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Query 17 (07/15/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The frequency is hardcoded to 4 seconds: https://github.com/mongodb/mongo/blob/b47deb5910ac97ed1741efad08d5e4a11bdd0740/src/mongo/db/clientcursor.cpp#L269 We would like to make this configurable, so that we can make it run more often in cursor_timeout.js. In that test, we wait 5 seconds for cursors to be killed, so since the background job runs every 4 seconds, this can be insufficient. Rather than waiting for longer (which will make the test take longer), we should make the background job frequency configurable. It would also be helpful to set verbosity to 1 in cursor_timeout.js, so that we can see the cursor IDs in case a cursors fails to be killed after we make this change. |
| Comments |
| Comment by Githook User [ 14/Jul/16 ] |
|
Author: {u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}Message: |