WIP: Session deployment - #22
Draft
thodson-usgs wants to merge 2 commits into
Draft
Conversation
thodson-usgs
marked this pull request as draft
February 26, 2024 22:30
thodson-usgs
force-pushed
the
session-mode
branch
from
February 27, 2024 04:42
3452a07 to
fb9ee8b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR would configure Flink to run in session mode. Essentially, it would create a single job manager for the cluster, and all
pangeo-forge-recipeswould submit their jobs to that job manager.One of the main advantages of this would be to centralize all infrastructure configuration configuration in
pangeo-forge-cloud-federation.Currently, infrastructure is spread across
pangeo-forge-cloud-federation,pangeo-forge-runnerand within the individual recipe'sconfig.py, and this makes it difficult to configure the cluster. Ideally, we could have multiple node pools of on demand and spot, instances, high-availability job managers, reactive scaling, default failure strategies, etc and set all that withinpangeo-forge-cloud-federation. Then the recipe andpangeo-forge-runnerrequire minimal configuration, like setting parallelism and the job name.