[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: |
|
||||||||
| 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: Instead of tracking the number of idle milliseconds, each ClientCursor |