[BEAM-9490] Environment may be cleaned up prematurely when using environment expiration

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.21.0
• Component/s: sdk-java-core
• Labels: Done
• Assignee: Maximilian Michels
• Reporter: Maximilian Michels
• Created: 12/Mar/20 14:51
• Updated: 06/Oct/20 21:50
• Resolved: 14/Mar/20 12:42

Description

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.

Issue Links

• links to: GitHub Pull Request #11108