929359291 opened a new issue, #3428:
URL: https://github.com/apache/incubator-streampark/issues/3428

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-streampark/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### Java Version
   
   11
   
   ### Scala Version
   
   2.12.x
   
   ### StreamPark Version
   
   2.1.2
   
   ### Flink Version
   
   1.17.1
   
   ### deploy mode
   
   yarn-application
   
   ### What happened
   
   
streampark任务超时后,web页面显示失败,yarn里面仍在运行,于是我使用映射作业功能发现不成功,任务一直处于mapping状态,观察日志后发现原来yarn
 
application部署下job_manager_url会动态更换,但是映射时只能填写appcationId和jobId,数据库中存储的job_manager_url是过期的要修改成正确后监听线程才能正常获取状态并更新到数据库。
   
   After the streampark task timed out, the web page displayed a failure and 
Yarn was still running. Therefore, I used the mapping job function to find that 
it was not successful and the task remained in the mapping state. After 
observing the logs, I found that the job was originally deployed under the Yarn 
application_ Manager_ The URL will be dynamically changed, but during mapping, 
only applicationId and jobId can be filled in, as well as the job stored in the 
database_ Manager_ The URL is expired and needs to be modified to be correct 
before the listening thread can obtain the status and update it to the database 
normally.
   
   
![image](https://github.com/apache/incubator-streampark/assets/33850806/65526ab1-2409-4a03-a09d-bed3e4224514)
   
   
   ### 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](https://www.apache.org/foundation/policies/conduct)
   


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