You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 18:00:02 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 ]

Kenneth Knowles updated BEAM-10959:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> 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
>          Time Spent: 9.5h
>  Remaining Estimate: 0h
>
> 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)