Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug] [运维中心] 在dinky正常运行，作业发布后，如果作业一直running，但是flink集群关闭情况下，运维中心重启后获取到作业状态一直running #700

Closed
2 of 3 tasks
qzgt opened this issue Jul 7, 2022 · 8 comments
Closed
2 of 3 tasks

[Bug] [运维中心] 在dinky正常运行，作业发布后，如果作业一直running，但是flink集群关闭情况下，运维中心重启后获取到作业状态一直running #700

qzgt opened this issue Jul 7, 2022 · 8 comments
Labels
Bug Something isn't working
Milestone
0.7.0

Comments

@qzgt
Copy link

qzgt commented Jul 7, 2022

Search before asking

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

What happened

在dinky正常运行，作业发布后，如果作业状态一直running，但是flink集群关闭情况下，运维中心重启后获取到作业状态一直running。

What you expected to happen

希望运维中心的状态根据实时的进行，同时支持以dinky端数据为主，即如果dinky原来的作业状态为running状态，但是flink集群没有对应job或者已经关闭，那么dinky可以自动重启一个job。

How to reproduce

直接在dinky-admin web端提交任务，然后直接关闭flink集群，然后重新启动dinky就可以复现。

Anything else

No response

Version

0.6.5

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct
@qzgt qzgt added Bug Something isn't working Waiting for reply Waiting for reply labels Jul 7, 2022
@aiwenmo
Copy link
Contributor

aiwenmo commented Jul 7, 2022

请附截图

@aiwenmo aiwenmo removed the Waiting for reply Waiting for reply label Jul 7, 2022
@JerryLen
Copy link

+1

@qzgt qzgt closed this as completed Jul 11, 2022
@qzgt
Copy link
Author

qzgt commented Jul 11, 2022

请附截图

截图如下：

微信截图_20220711103914
微信截图_20220711103936

@qzgt qzgt reopened this Jul 11, 2022
@aiwenmo
Copy link
Contributor

aiwenmo commented Jul 11, 2022

这是正常的，因为由于意外原因无法请求到jobmanager，所以无法获取最新的算子状态，默认不更新，即还是RUNNING。

@JerryLen
Copy link

意外原因无法请求到jobmanager，个人认为默认更新为UNKNOWN可能更合理些，是希望平台能够管理监控任务的，变为UNKNOWN告警好去检查异常

@aiwenmo
Copy link
Contributor

aiwenmo commented Jul 12, 2022

任务实例状态已经更新为 UNKNOWN 了

@chen5306514
Copy link

我认为job instance的状态 和job history的状态应该保持一致才对，不然会出现状态不一致导致用户出现迷惑

@aiwenmo aiwenmo added this to the 0.6.7 milestone Aug 3, 2022
@aiwenmo aiwenmo modified the milestones: 0.6.7, 0.6.8 Aug 30, 2022
@aiwenmo
Copy link
Contributor

aiwenmo commented Nov 19, 2022

@aiwenmo aiwenmo closed this as completed Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Something isn't working
Projects
Dinky Roadmap
Archived in project
Milestone
0.7.0
Development

No branches or pull requests
4 participants
@qzgt @chen5306514 @aiwenmo @JerryLen