-
Notifications
You must be signed in to change notification settings - Fork 6
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
Need a persistent efs volume for storing Flink metadata #17
Comments
thodson-usgs
changed the title
Add a persistent efs volume for storing Flink metadata
Need a persistent efs volume for storing Flink metadata
Jan 29, 2024
Open
@thodson-usgs #6 sets up an EFS that can be consumed this way! Maybe you can work with @ranchodeluxe on that? |
Sure, I'll start rebasing that branch onto main |
@thodson-usgs: since that other PR merged do we still need this one? Or maybe a version of it? |
Sure. I think we can close this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To recover from job-manager failures, Flink needs a persistent file system for storing job metadata. This could be s3 or efs. Of those two, I have a slight preference for the latter, because USGS uses sessions, so the cluster might lose s3 access during the course of a long job.
I'm looking into how to add a persistent volume to our k8 deployment but keep finding myself down Medium rabbit holes.
The text was updated successfully, but these errors were encountered: