[SERVER-47396] Improve message for timeout in kill_pinned_cursor.js Created: 07/Apr/20  Updated: 29/Oct/23  Resolved: 07/Apr/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Charlie Swanson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Query 2020-04-20
Participants:
Linked BF Score: 17

 Description   

We've observed one failure to close all open cursors. I suspect it's because some internal operations are opening cursors and interfering with the test, so logging which operations remain active with open cursors at the end of the test will hopefully let us confirm or deny that theory.

I was unable to reproduce the issue so I'd like to commit the improved diagnostic message and wait for it to happen again.



 Comments   
Comment by Githook User [ 08/Apr/20 ]

Author:

{'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}

Message: SERVER-47396 Improve kill_pinned_cursor.js diagnostic logging

(cherry picked from commit 402533f1804fc7b22c9cb09fad8f4f788e35f994)
Branch: v4.4
https://github.com/mongodb/mongo/commit/373feb6cc7cf0731b4a7659d4890110644c788f8

Comment by Githook User [ 07/Apr/20 ]

Author:

{'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}

Message: SERVER-47396 Improve kill_pinned_cursor.js diagnostic logging
Branch: master
https://github.com/mongodb/mongo/commit/402533f1804fc7b22c9cb09fad8f4f788e35f994

Generated at Thu Feb 08 05:14:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.