[SERVER-62889] Cursor gets deleted despite it is in use Created: 22/Jan/22 Updated: 27/Oct/23 Resolved: 27/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexander Paderin | Assignee: | Dmitry Agranat |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Later, i will try to provide snippet how to reproduce it |
| Participants: |
| Description |
|
First of all, it doesn't seems issue https://jira.mongodb.org/browse/SERVER-34810 is fixed for Mongo 5.x version. I use Mongo 5.0.3 and keep getting ``` {"t":\{"$date":"2022-01-21T22:49:37.910+03:00"},"s":"I", "c":"QUERY", "id":20528, "ctx":"LogicalSessionCacheRefresh","msg":"Killing cursor as part of killing session(s)","attr":{"cursorId":1860156630682855801}} ```
|
| Comments |
| Comment by Dmitry Agranat [ 27/Jan/22 ] |
|
Happy to hear you've figured this out apocarteres@gmail.com! |
| Comment by Alexander Paderin [ 26/Jan/22 ] |
|
hi Dmitry. Sorry for stealing your time, seems the issue was on my side, i used custom compiled mongo with some local hacks i needed to PoC. Seems it did trigger the undesired behavior. Fee lfree to close this task!
My appologies and have a great day! |
| Comment by Dmitry Agranat [ 23/Jan/22 ] |
|
apocarteres@gmail.com, I think the If you could provide a simple reproducer, that would be great. Thanks, |