nicoweidner opened a new pull request #17762:
URL: https://github.com/apache/flink/pull/17762


   ## What is the purpose of the change
   
   *Add a configuration option that allows to keep the cluster running after 
the application finishes in application mode. The default value is set to false 
(meaning that the cluster will shut down), so current behavior is unaffected.*
   
   
   ## Brief change log
   
     - *Added config option execution.shutdown-on-application-finish*
     - *Refactored code in ApplicationDispatcherBootstrap and corresponding 
tests to make it easier to understand/modify and reduce duplication*
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *Added unit tests in ApplicationDispatcherBootstrapTest that verify 
cluster shutdown is not called if the configuration option is enabled*
     - *Can be tested manually by starting a job in application mode with the 
new config option enabled, then cancelling the job. The cluster and Web UI stay 
alive and can be terminated via a call to 
https://nightlies.apache.org/flink/flink-docs-master/docs/ops/rest_api/#cluster*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? only via config option description
   


-- 
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]


Reply via email to