[SERVER-36890] Don't call vivify Created: 27/Aug/18 Updated: 27/Oct/23 Resolved: 19/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Blake Oler |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backport Requested: |
v4.0, v3.6
|
||||
| Sprint: | Sharding 2018-09-24 | ||||
| Participants: | |||||
| Description |
|
LogicalSessionCache should not refer to the CursorManager to get all open sessions. The session initialization code must guarantee that LogicalSessionsCache is in sync with CursorManager managed cursors. |
| Comments |
| Comment by Misha Tyulenev [ 19/Sep/18 ] |
|
the call to vivify in killCursor and getMore is justified because the last use field will be updated so the cursor will remain active. In the case killCursor fails its needed to prevent recurring calls each session refresh cycle. |