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.

Sign up for GitHub

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

Jump to bottom

Create a new cluster before deleting the old one on the job update #590

Open
JuliaBogdan opened this issue Jan 5, 2023 · 0 comments
Open

Create a new cluster before deleting the old one on the job update #590

JuliaBogdan opened this issue Jan 5, 2023 · 0 comments

Comments

@JuliaBogdan
Copy link

JuliaBogdan commented Jan 5, 2023 •
edited
Loading

When updating the streaming job, we need to minimize the disruption time that comes from the Flink cluster re-creation.

One option to address it might look like blue-green deployment:

  1. Flink operator receives an update request
  2. A new cluster is created
  3. When the new cluster is ready, the operator triggers savepoint (if JobSpec.takeSavepointOnUpdate: true) and stops the old job
  4. When savepoint is taken, the new job starts in the new cluster.

An important requirement is that two identical jobs should not run simultaneously.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JuliaBogdan