[
https://issues.apache.org/jira/browse/FLINK-31529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weihua Hu updated FLINK-31529:
------------------------------
Description:
Currently the YarnClusterDescriptor always wait yarn application status to be
RUNNING even if we use the detach mode.
In batch mode, the queue resources is insufficient in most case. So the job
manager may take a long time to wait resources. And client also keep waiting
too. If flink client is killed(some other reason), the cluster will be shutdown
too.
We need an option to let Flink client exit early. Use the detach option or
introduce a new option are both OK.
Looking forward other suggestions
was:
Currently the YarnClusterDescriptor always wait yarn application status to be
RUNNING even if we use the detach mode.
In batch mode, the queue resources is insufficient in most case. So the job
manager may take a long time to wait resources. And client also keep waiting
too.
> Let yarn client exit early before JobManager running
> ----------------------------------------------------
>
> Key: FLINK-31529
> URL: https://issues.apache.org/jira/browse/FLINK-31529
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: Weihua Hu
> Priority: Major
>
> Currently the YarnClusterDescriptor always wait yarn application status to be
> RUNNING even if we use the detach mode.
> In batch mode, the queue resources is insufficient in most case. So the job
> manager may take a long time to wait resources. And client also keep waiting
> too. If flink client is killed(some other reason), the cluster will be
> shutdown too.
> We need an option to let Flink client exit early. Use the detach option or
> introduce a new option are both OK.
> Looking forward other suggestions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
