Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Linked BF Score:
29
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

See discussion on BF-27364 for more details:

Instead of doing the auto-kill upon unpinning when
cursor->cameFromRouter() && interruptStatus == ErrorCodes::MaxTimeMSExpired, could we set a flag on the cursor indicating that it has been killed in killCursor and check that to determine whether we should destruct it immediately in unpin?

is caused by

SERVER-67722 Shard cursor is not killed on MaxTimeMSExpired

Closed

Assignee:: Alyssa Clark
Reporter:: Alyssa Clark
Participants:: Alyssa Clark, Githook User, Romans Kasperovics
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jan 12 2023 06:14:40 PM UTC
Updated:: Oct 29 2023 09:28:19 PM UTC
Resolved:: Jan 18 2023 03:07:15 PM UTC
Confidence Status Last Update:: 12/Jan/23 6:17 PM