Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Minor - P4
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Confidence Status:
None

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

The current behavior of not running killCursors after a network error was implemented in ~~PYTHON-322~~ to prevent "_pinValue assertion on some server releases". I believe this was for MongoDB 2.0 or 2.2 and it's no longer relevant on modern server versions but we should double check before making any change.

is caused by

PYTHON-322 Sometimes causes _pinValue assertion in db

Closed

is related to

DRIVERS-2990 Clarify that drivers should kill cursors after timeout errors

Needs Triage

related to

PYTHON-3953 PyMongo should send killCursors on MaxTimeMSExpired Error

Closed

DRIVERS-2751 Update spec tests to reflect new killCursor behavior for ConnectionFailure

Closed

Assignee:: Unassigned
Reporter:: Shane Harvey
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Feb 23 2019 12:24:46 AM UTC
Updated:: Sep 25 2024 05:39:32 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates