[SERVER-28604] Log when a cursor is reaped for exceeding the timeout Created: 04/Apr/17 Updated: 21/Oct/19 Resolved: 11/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.15, 4.1.4, 4.0.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Ted Tuckman |
| Resolution: | Done | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.0, v3.6, v3.4
|
||||||||
| Sprint: | Query 2018-10-22 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Sometimes, queries fail because a cursor cannot be found. It would be really useful to see in the mongod logs when a cursor is reaped, to determine if that cursor was lost due to timeout. As a part of this ticket, we should consider updating mongos to only log when a cursor is reaped (and not when it is merely marked for deletion, which is annoying for pinned cursors, which will not be timed out). |
| Comments |
| Comment by Githook User [ 21/Oct/19 ] |
|
Author: {'username': 'TedTuckman', 'email': 'ted.tuckman@mongodb.com', 'name': 'Ted Tuckman'}Message: (cherry picked from commit 480af6017647716bd2d087c6d772ef44db47c4cc) |
| Comment by Githook User [ 21/Oct/19 ] |
|
Author: {'name': 'Ted Tuckman', 'username': 'TedTuckman', 'email': 'ted.tuckman@mongodb.com'}Message: (cherry picked from commit 480af6017647716bd2d087c6d772ef44db47c4cc) |
| Comment by Githook User [ 11/Oct/18 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |
| Comment by Kyle Suarez [ 04/Apr/17 ] |
|
If we decide to do this, please consider backporting this to v3.4 (although david.storch has reservations). |