-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
Pymongo uses a different implicit session for each cursor returned from the parallelCollectionScan command. This worked fine in 3.6 but in 4.0 the getMore with a different lsid fails with:
OperationFailure: Cannot run getMore on cursor 625787356667, which was created in session fa0f13b5-db90-49fa-9d93-f0633db9289a - 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=, in session 6b6390df-a5af-4b56-b942-683a2ee9cf02 - 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
Is Pymongo's approach wrong, should we always use the same session for all the resulting cursors?
- duplicates
-
SERVER-34417 parallelCollectionScan within a session errors under auth
- Closed