Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BEAM-9490] Guard referencing for environment expiration via a lock #11108

Merged
merged 2 commits into from
Mar 14, 2020

Conversation

mxm
Copy link
Contributor

@mxm mxm commented Mar 12, 2020

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.

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- Build Status --- --- Build Status
Java Build Status Build Status Build Status
Build Status
Build Status
Build Status
Build Status
Build Status Build Status Build Status
Build Status
Build Status
Python Build Status
Build Status
Build Status
Build Status
--- Build Status
Build Status
Build Status
Build Status
Build Status
--- --- Build Status
XLang --- --- --- Build Status --- --- Build Status

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website
Non-portable Build Status Build Status
Build Status
Build Status Build Status
Portable --- Build Status --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Copy link
Contributor Author

@mxm mxm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tweise Please have a look. Open to suggestions if you have another idea how to fix this (the race condition).

@mxm mxm force-pushed the BEAM-9490 branch 2 times, most recently from d9bf4d7 to 55b3268 Compare March 12, 2020 16:42
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.
@mxm
Copy link
Contributor Author

mxm commented Mar 13, 2020

@tweise Any comments? I've been running this on a cluster for a day with a 15 minute environment expiration. Haven't seen any problems with regards to the environment expiration.

@tweise
Copy link
Contributor

tweise commented Mar 13, 2020

@mxm I'm looking at this and will get back.

@tweise
Copy link
Contributor

tweise commented Mar 13, 2020

Run Python2_PVR_Flink PreCommit

@mxm mxm merged commit bdd1726 into apache:master Mar 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants