[SERVER-28410] ClientCursor timeout period should not include time spent executing previous getMore Created: 21/Mar/17  Updated: 14/Apr/17  Resolved: 14/Apr/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: James Wahlin Assignee: Charlie Swanson
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-19892 Cursor idle time should be calculated... Closed
Operating System: ALL
Participants:

 Description   

When a getMore is executed, we reset the cursor's "idle time" value to 0 prior to plan execution. We then increment this value via ClientCursorMonitor thread during plan execution. This means that a cursor returned by getMore will have 10 minutes minus getMore execution time left before timing out. A getMore command/op that runs for 5 minutes will be left with 5 minutes until timeout on return to the client. A getMore that runs for 10 minutes will be eligible for immediate timeout. We should instead start the timeout period at the time the ClientCursor is unpinned.

A fix for this issue should take SERVER-28327 into account, as it will likely change the mechanism we use to timeout cursors on mongod.


Generated at Thu Feb 08 04:18:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.