[SERVER-80001] Delist opCtx during ClientDisconnect during getMores Created: 15/Aug/23 Updated: 29/Oct/23 Resolved: 24/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alex Li | Assignee: | Alex Li |
| Resolution: | Fixed | 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 | ||||||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||||||
| Sprint: | Service Arch 2023-08-21, Service Arch 2023-09-04 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 120 | ||||||||||||||||||||
| Description |
|
checkForInterruptNoAssert calls during handleRequest for getMores that result in ClientDisconnect (being thrown and markKilled) cause an issue where a new killCursor opCtx is created and the old opCtx is not delisted. Find a way to change this if condition for this exact condition, possibly making a more clear distinction between thrown statuses and opCtx killStatus. ServiceEntryPointImpl delist logic |
| Comments |
| Comment by Githook User [ 12/Oct/23 ] |
|
Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'}Message: (cherry picked from commit a538c12b922ef26e721135be51badcff68dfc336) |
| Comment by Githook User [ 24/Aug/23 ] |
|
Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'}Message: |