Mongo cursor timeout leads to CursorNotFound error
Open
bug
io
mongodb
P3
python
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
If some work items take a lot of processing time and the cursor of a bundle is not queried for too long, then mongodb will timeout the cursor which results in
```
pymongo.errors.CursorNotFound: cursor id ... not found
```
Imported from Jira [BEAM-10002](https://issues.apache.org/jira/browse/BEAM-10002). Original Jira may contain additional context.
Reported by: corvin.
Contributor guide
Research direction
The issue names no file, test, or entry point. Start by locating the MongoDB cursor handling and a test or reproduction for long-running work items; done means processing does not fail with pymongo.errors.CursorNotFound when a cursor is not queried for a long time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100