-
Notifications
You must be signed in to change notification settings - Fork 9
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
Flink Historyserver for Async Job Status #122
Comments
Good call! And related to #20 where we discuss the possibility of adding a generic (@ranchodeluxe for your context, the |
Mount EFS to Job Managers so they can archive jobs for historical status lookups Addresses #122 Related PR: pangeo-forge/pangeo-forge-cloud-federation#6 Co-authored-by: ranchodeluxe <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Problem
We shouldn't have to run
kubectl logs -f pod/<job-manager-pod> | grep 'Job BeamApp-flink-.*RUNNING to.*'
to know if a job succeeded for failed. We want to poll against something asyncGoal
Figure out how to set up and configure the HistoryServer
The text was updated successfully, but these errors were encountered: