-
Type: New Feature
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Reads
-
None
Currently, slow operations that take a long time to process a cursor can timeout in Spark.
As we wrap the cursor we could survive a cursor timeout by creating a new cursor.
- is related to
-
SPARK-137 com.mongodb.MongoCursorNotFoundException: Query failed with error code -5
- Closed
-
SPARK-139 com.mongodb.mongoCusorNotFoundException
- Closed
-
SPARK-171 Using MongoSparkConnector in hadoop- Exception in thread "main" com.mongodb.MongoCommandException: Command failed with error 13127: 'cursor id 42591143425 didn't exist on server.'
- Closed