zuston opened a new pull request #18220:
URL: https://github.com/apache/flink/pull/18220


   …mode on Yarn
   
   ## What is the purpose of the change
   
   ### Why
   In our internal streaming platform, we will use flink-cli tool to submit 
Flink streaming application on Yarn.
   
   However when encountering Hadoop cluster down and then lots of flink apps 
need to be resubmitted, the submitter of worker in our platform will hang at 
this time.
   
   Because the Yarn cluster resources are tight and the scheduling efficiency 
becomes low when lots of apps needs to be started.
   
   And flink-cli will not exit until the app status changes to running.
   
   In addition, I also think there is no need to wait when app status is 
accepted with detach mode on Yarn.
   
   ## Brief change log
   
   Introduce the `AsyncClusterClientProvider` that allows to wait for the 
submission result if users need to create a ClusterClient.
   
   ## Verifying this change
   
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / **no** / don't 
know)
     - The S3 file system connector: (yes / no / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs 
/ not documented)
   


-- 
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: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to