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.

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

[Bug] When Flink is running in yarn mode, the number of taskmanagers and memory size cannot be accurately obtained #4114

Open
3 tasks done
wangkeshuai1 opened this issue Oct 15, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@wangkeshuai1
Copy link
Contributor

Search before asking

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

Java Version

1.8.0_345

Scala Version

2.12.x

StreamPark Version

2.1.5

Flink Version

Flink-1.16.2

deploy mode

yarn-application

What happened

This issue is similar to #1633 .
I learned from the debug source code that when I got the data of Flink Overview, the data was not accurate because Flink had just started, and the data obtained by debug was shown in the following figure.

Error Exception

No response

Screenshots

image
image

Are you willing to submit PR?

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

Code of Conduct

@wangkeshuai1 wangkeshuai1 added the bug Something isn't working label Oct 15, 2024
@wangkeshuai1
Copy link
Contributor Author

I want to submit this PR, the idea is to delete the first judgment, because I think these information need to be obtained in real time, for example, the end time of different TM may be different, if this judgment is deleted, STARTING_CACHE will be deleted at the same time, because this cache is not referenced elsewhere, may I ask if this cache still needs to be retained?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant