[Bug] fail to submit a yarn-session task

[Mortal-dx]

Search before asking

• [X] I had searched in the issues and found no similar issues.

Java Version

1.8

Scala Version

2.12.x

StreamPark Version

2.1.0

Flink Version

1.16

deploy mode

yarn-session

What happened

step 1、configuration and start a yarn -session at streampark,we can see the yarn-session task nomal at yarn webui stetp 2、release a yarn-session task result ：Failed Detail exception: org.apache.streampark.console.base.exception.ApiAlertException: the target cluster is unavailable, please check! at org.apache.streampark.console.core.service.impl.ApplicationServiceImpl.checkEnv(ApplicationServiceImpl.java:434) at org.apache.streampark.console.core.service.impl.ApplicationServiceImpl$$FastClassBySpringCGLIB$$56060f90.invoke() at

step 1、configuration and start a yarn -session at streampark,we can see the yarn-session task nomal at yarn webui stetp 2、stop the yarn-session result : current cluster is not active, please check

Error Exception

No response

Screenshots

No response

Are you willing to submit PR?

• [ ] Yes I am willing to submit a PR!(您是否要贡献这个PR?)

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[xujiangfeng001]

Hi @Dsrong ,thank you very much for your feedback. I would like to ask if this issue is inevitable or occasional. I reproduced it using your method, but it was not successful. May I ask if there is excessive pressure on the resourceManager in this situation.

[xiaomi-box]

@xujiangfeng001 Hello, I also encounter the same problem. I feel that the time it takes for the page to determine the cluster startup status is too short, and the page returns startup failure. As a result, the cluster cannot be found when the task is executed

[xujiangfeng001]

@xujiangfeng001 Hello, I also encounter the same problem. I feel that the time it takes for the page to determine the cluster startup status is too short, and the page returns startup failure. As a result, the cluster cannot be found when the task is executed

hi @xiaomi-box ,you can try the latest version, as far as I know, this issue has been resolved

[wolfboys]

fixed in 2.1.4