-
Notifications
You must be signed in to change notification settings - Fork 13k
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
[WIP] PoC add jobName and jobId tag in jobMananger process metric #15916
base: master
Are you sure you want to change the base?
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit 3be4eb0 (Sat Aug 28 12:10:31 UTC 2021) Warnings:
Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for creating this PR @qqibrow. I think that the solution does not generalize well because it relies on the fact that there is a file based JobGraph
present. Moreover, it moves per-job-cluster specific behavior into the general ClusterEntrypoint
which violates the separation of concerns.
FileJobGraphRetriever fileJobGraphRetriever = | ||
FileJobGraphRetriever.createFrom(configuration, null); | ||
|
||
String jobName = null; | ||
String jobId = null; | ||
try { | ||
JobGraph jobGraph = fileJobGraphRetriever.retrieveJobGraph(configuration); | ||
jobName = jobGraph.getName(); | ||
jobId = jobGraph.getJobID().toHexString(); | ||
} catch (FlinkException e) { | ||
LOG.info("Not able to fetch JobGraph"); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this only works for the Yarn per job cluster entrypoint and is not a general solution. For example, the application mode won't be supported. Hence, I think we cannot do it like this.
@tillrohrmann Thanks for reviewing! If so, do you have any recommendation where I can add this change? |
https://issues.apache.org/jira/browse/FLINK-22164