[SERVER-40110] ClusterCursorManager::CursorEntry::isKillPending() should not call checkForInterrupt Created: 13/Mar/19 Updated: 29/Oct/23 Resolved: 29/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 4.0.0 |
| Fix Version/s: | 4.0.13, 4.2.1, 4.3.1 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Mira Carey | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v4.2, v4.0
|
||||||||||||||||||||||||
| Sprint: | Query 2019-04-08, Query 2019-04-22, Query 2019-05-06, Query 2019-05-20, Query 2019-06-03, Query 2019-06-17, Query 2019-07-01, Query 2019-07-15, Query 2019-07-29, Query 2019-08-12 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 30 | ||||||||||||||||||||||||
| Description |
is calling checkForInterruptNoAssert. That's a problem because:
I think this doesn't usually come up because the ops using cluster cursors usually haven't exceeded maxtimems. That may be an avenue for an isolated repro. |
| Comments |
| Comment by Githook User [ 09/Sep/19 ] |
|
Author: {'name': 'Ian Boros', 'username': 'puppyofkosh', 'email': 'ian.boros@mongodb.com'}Message: This commit also includes a modification to the test done under |
| Comment by Githook User [ 06/Sep/19 ] |
|
Author: {'name': 'Ian Boros', 'username': 'puppyofkosh', 'email': 'ian.boros@mongodb.com'}Message: This commit also includes a modification to the test done under |
| Comment by Githook User [ 26/Jul/19 ] |
|
Author: {'name': 'Ian Boros', 'username': 'puppyofkosh', 'email': 'puppyofkosh@gmail.com'}Message: |