You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/03 17:07:02 UTC

[jira] [Commented] (BEAM-10002) Mongo cursor timeout leads to CursorNotFound error

    [ https://issues.apache.org/jira/browse/BEAM-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170194#comment-17170194 ] 

Beam JIRA Bot commented on BEAM-10002:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Mongo cursor timeout leads to CursorNotFound error
> --------------------------------------------------
>
>                 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: Corvin Deboeser
>            Priority: P2
>              Labels: stale-assigned
>
> 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)