You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Luke Cwik (Jira)" <ji...@apache.org> on 2020/09/23 20:45:00 UTC

[jira] [Updated] (BEAM-10959) Fix race where split/progress calls return "Unknown process bundle instruction"

     [ https://issues.apache.org/jira/browse/BEAM-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luke Cwik updated BEAM-10959:
-----------------------------
    Summary: Fix race where split/progress calls return "Unknown process bundle instruction"  (was: Fix race where split/progress calls return "Unknown process bundle instruction" since initialization of BundleProcessor happens in a separate thread)

> Fix race where split/progress calls return "Unknown process bundle instruction"
> -------------------------------------------------------------------------------
>
>                 Key: BEAM-10959
>                 URL: https://issues.apache.org/jira/browse/BEAM-10959
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-harness
>            Reporter: Luke Cwik
>            Assignee: Luke Cwik
>            Priority: P2
>
> Currently there is a race where a BundleProcessor doesn't exist until another thread picks up the task and inserts into the active set. This allows for split/progress calls to happen and error out with "Unknown process bundle instruction X".
> Since the control stream is ordered, we can guarantee that an uninitialized BundleProcessor exists that can respond to this really early split/progress calls.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)