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/03/14 12:43:00 UTC

[jira] [Resolved] (BEAM-9490) Environment may be cleaned up prematurely when using environment expiration

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

Maximilian Michels resolved BEAM-9490.
--------------------------------------
    Fix Version/s: 2.21.0
       Resolution: Fixed

> Environment may be cleaned up prematurely when using environment expiration
> ---------------------------------------------------------------------------
>
>                 Key: BEAM-9490
>                 URL: https://issues.apache.org/jira/browse/BEAM-9490
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Major
>             Fix For: 2.21.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When environment expiration is configured, environments are removed from a cache map after some amount of time. This cache map may be accessed by multiple ExecutableStage transforms in parallel. During environment expiration there is a small time window which allows for an environment to still being used while another transform removes, dereferences, and closes the environment. This is not expected behavior.



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