It is very unexpected that a cursor created with no_cursor_timeout=True can still timeout (as described in DOCS-11255 and PYTHON-1879). We should raise an informative warning in this case:
>>> client.t.t.find(no_cursor_timeout=True)
__main__:1: UserWarning: use an explicit session with no_cursor_timeout=True otherwise the cursor may still timeout after 30 minutes, for more info see DOCS-11255
<pymongo.cursor.Cursor object at 0x10aef82b0>
- related to
-
PYTHON-1879 no_cursor_timeout not functioning as expected
-
- Closed
-
-
DOCS-11255 Document that 3.6 implicit sessions may cause noTimeout cursors to close while in use.
-
- Closed
-