[ 
https://issues.apache.org/jira/browse/FLINK-15264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-15264:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: 
auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Job Manager TASK_SLOTS_TOTAL metrics does not shows the Job ID
> --------------------------------------------------------------
>
>                 Key: FLINK-15264
>                 URL: https://issues.apache.org/jira/browse/FLINK-15264
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>    Affects Versions: 1.8.1
>            Reporter: xiaogang zhou
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>         Attachments: image-2019-12-17-17-01-51-826.png
>
>
> I am running the Single flink Job mode on Yarn. As each Job has a Job manager 
> running some where in the host of the yarn. Sometimes different Job managers 
> can running on the same host, and the metrics TASK_SLOTS_TOTAL has no 
> identification to show which job they are belonging.
>  
> Can we support a metric which can tell how many slots each job occupies? like 
> put a job-id description in TASK_SLOTS_TOTAL, or add another seperate 
> metrics. 
>  
> [~chesnay]  seems you helped lots of people in the runtime/metrics section. 
> let me know your opinion, or you can tell me any existing solution to solve 
> the problem. Thanks a lot



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to