You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
We are new to using the operator and have been running a few jobs in production. We don't have HA mode enabled yet and have observed that a few times after our JM crashes and we redeploy the application, the new job doesn't start from a savepoint. In a few cases the fromSavePoint location seems to be automatically set by the operator (we see this in the arguments to flink-submit). Where in Kubernetes can I inspect the state that the operator is using when I kick off new deployments.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
We are new to using the operator and have been running a few jobs in production. We don't have HA mode enabled yet and have observed that a few times after our JM crashes and we redeploy the application, the new job doesn't start from a savepoint. In a few cases the
fromSavePoint
location seems to be automatically set by the operator (we see this in the arguments toflink-submit
). Where in Kubernetes can I inspect the state that the operator is using when I kick off new deployments.The text was updated successfully, but these errors were encountered: