[SERVER-34395] Transaction killCursor enhancements allowed for when all cursors are globally managed Created: 09/Apr/18 Updated: 27/Oct/23 Resolved: 08/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
Address TODO statements that reference this ticket. Work will included:
|
| Comments |
| Comment by Tess Avitabile (Inactive) [ 08/Jun/18 ] |
|
These changes are no longer necessary, since we no longer attempt to close transaction cursors when the transaction ends: |
| Comment by Gregory McKeon (Inactive) [ 20/Apr/18 ] |
|
david.storch sending this over to you and putting it in the epic because James did the work initially. |
| Comment by Tess Avitabile (Inactive) [ 13/Apr/18 ] |
|
We can also avoid the out parameter canKillCursors in session.cpp, since we will be able to run _killTransactionCursors() while holding the client lock and/or the session mutex. |