[SERVER-4559] when a cursor is timed out, other cursors may last longer than they should Created: 26/Dec/11 Updated: 11/Jul/16 Resolved: 29/Dec/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 2.1.1 |
| Fix Version/s: | 2.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
ClientCursor::idleTimeReport checks for timeouts in two loops. The timing information is only provided in the first loop, and because the first loop is short circuited the timing information may not be provided to all cursors. for ( CCById::iterator i = clientCursorsById.begin(); i != clientCursorsById.end(); ) { } ... for ( CCById::iterator i = clientCursorsById.begin(); i != clientCursorsById.end(); ) { } |
| Comments |
| Comment by Dwight Merriman [ 28/Dec/11 ] |
|
glad you noticed. important. |
| Comment by auto [ 28/Dec/11 ] |
|
Author: {u'login': u'dwight', u'name': u'dwight', u'email': u'dwight@10gen.com'}Message: |
| Comment by Dwight Merriman [ 28/Dec/11 ] |
|
glad you found this. do we have a timeout test? i guess it hasn't manifested. |