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

[bitnami/flink] persistence config #31812

Closed
pisko1979 opened this issue Feb 6, 2025 · 3 comments
Closed

[bitnami/flink] persistence config #31812

pisko1979 opened this issue Feb 6, 2025 · 3 comments
Assignees
Labels

Comments

@pisko1979
Copy link

Name and Version

bitnami/flink 1.4.2

What is the problem this feature will solve?

Hi all
using latest helm chart for flink, i can not see any way to make Flink use persistent storage to persist state of jobs etc.
now after restart every job is lost.

any related config that you can point me?
thanks

regards
pisko

What is the feature you are proposing to solve the problem?

Persistent volumes to persist job states and history

What alternatives have you considered?

No response

@github-actions github-actions bot added the triage Triage is needed label Feb 6, 2025
@javsalgar javsalgar changed the title Flink persistence config [bitnami/flink] persistence config Feb 7, 2025
@github-actions github-actions bot removed the triage Triage is needed label Feb 7, 2025
@github-actions github-actions bot assigned juan131 and unassigned javsalgar Feb 7, 2025
@juan131
Copy link
Contributor

juan131 commented Feb 10, 2025

Hi @pisko1979

You need to configure "Checkpoints" in order to store the state of jobs on "state backends" which basically supports two types "HashMapStateBackend" (saved in JVM heap memory) and "EmbeddedRocksDBStateBackend" (key-value store):

Please note this chart doesn't support deploying a key-value store in case you want to use a "EmbeddedRocksDBStateBackend", hence you need to deploy it independently.

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Feb 26, 2025
Copy link

github-actions bot commented Mar 3, 2025

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@github-actions github-actions bot added the solved label Mar 3, 2025
@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants