You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Maximilian Michels (Jira)" <ji...@apache.org> on 2020/01/23 19:45:00 UTC

[jira] [Updated] (BEAM-9161) Inconsistent view of curent of ActiveBundle from main and bundle timer thread

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

Maximilian Michels updated BEAM-9161:
-------------------------------------
    Summary: Inconsistent view of curent of ActiveBundle from main and bundle timer thread  (was: Concurrent close of ActiveBundle from main and bundle timer thread)

> Inconsistent view of curent of ActiveBundle from main and bundle timer thread
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-9161
>                 URL: https://issues.apache.org/jira/browse/BEAM-9161
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The issue results in exceptions like "Already closed" due to a concurrent close of the remote input receivers from (1) the main thread and (2) the thread for finishing the bundle. In combination with the {{bundleFinishedCallback}} it may have also caused a slowdown due to closing a bundle when it was not needed.
> We should make sure that only one thread at a time can start or finish a bundle.



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