rmetzger commented on code in PR #1216: URL: https://github.com/apache/flink-kubernetes-operator/pull/1216#discussion_r4166003527
########## docs/content/docs/managing/job-management.md: ########## @@ -68,7 +68,7 @@ job: state: suspended ``` -Setting the value to `suspended` stops the job while keeping its state information, and setting it back to `running` resumes the job from where it stopped. Any other spec change while the job is running triggers an [upgrade](#upgrades), and changes made while suspended are recorded and take effect once the job is resumed. In every case, how state survives the stop and restore is decided by the upgrade mode. +Setting the value to `suspended` stops the job while keeping its state information, and setting it back to `running` resumes the job from where it stopped. Any other spec change while the job is running triggers an [upgrade](#upgrades), and changes made while suspended are recorded and take effect once the job is resumed. In every case, how state survives the stop and restore is decided by the upgrade mode. A [savepoint redeploy](#redeploying-from-a-savepoint) requested while suspended is the exception: resuming starts from its `initialSavepointPath` regardless of the upgrade mode. Review Comment: > resuming starts from its `initialSavepointPath` regardless of the upgrade mode. shouldn't this sentence rather be in the redeploying-from-a-savepoint section? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
