[SERVER-28328] ClientCursor::_idleAgeMillis update is racy Created: 15/Mar/17  Updated: 06/Dec/17  Resolved: 03/May/17

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

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

Issue Links:
Related
related to SERVER-28327 ClientCursorMonitor can timeout curso... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

ClientCursor::_idleAgeMillis can be updated both by the ClientCursorMonitor thread (when recording lapsed time) and by a request thread executing a getMore command/op (when resetting via resetIdleTime() call). It is currently not protected from concurrent writes but should be.



 Comments   
Comment by Githook User [ 03/May/17 ]

Author:

{u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}

Message: SERVER-28327 Revamp cursor timeout logic.

Instead of tracking the number of idle milliseconds, each ClientCursor
tracks its last time of use. This also resolves related issues
SERVER-28328 and SERVER-19892.
Branch: master
https://github.com/mongodb/mongo/commit/7759c61a35f835aa109131b8f1575f0e1879cba0

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