You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Corvin Deboeser (Jira)" <ji...@apache.org> on 2020/05/15 03:11:00 UTC
[jira] [Updated] (BEAM-10002) Cursor not found if work items take a
long time
[ https://issues.apache.org/jira/browse/BEAM-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Corvin Deboeser updated BEAM-10002:
-----------------------------------
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
{code:java}
pymongo.errors.CursorNotFound: cursor id ... not found
{code}
was:
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
```
> Cursor not found if work items take a long time
> -----------------------------------------------
>
> Key: BEAM-10002
> URL: https://issues.apache.org/jira/browse/BEAM-10002
> Project: Beam
> Issue Type: Bug
> Components: io-py-mongodb
> Affects Versions: 2.20.0
> Reporter: Corvin Deboeser
> Assignee: Yichi Zhang
> Priority: Major
>
> 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
> {code:java}
> pymongo.errors.CursorNotFound: cursor id ... not found
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)