[
https://issues.apache.org/jira/browse/YARN-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323837#comment-16323837
]
Sunil G commented on YARN-7728:
-------------------------------
Thanks [~eepayne], this will be really helpful when preemption happens.
I have doubt w.r.t multiple resources scenario. In 3.0, we support multiple
types, and this covers only cpu and memory. So could we cover preemption
metrics also in case of multi resources.
One more doubt is with aggregateVcoreSecondsPreempted. MutableCounterLong is
used for this. But under one queue, we ll have multiple containers gets
preempted and each container resource size vary drastically. So are we looking
for an aggregate resource among all preempted containers in a given time ?
Minor Nits:
aggregateMegabyteSecondsPreempted: MegaByte seems a bit confusing, MemoryMB is
used in another places as well. Could we use something similar (like prepending
memory)
> Expose and expand container preemptions in Capacity Scheduler queue metrics
> ---------------------------------------------------------------------------
>
> Key: YARN-7728
> URL: https://issues.apache.org/jira/browse/YARN-7728
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.9.0, 2.8.3, 3.0.0
> Reporter: Eric Payne
> Assignee: Eric Payne
> Attachments: YARN-7728.001.patch
>
>
> YARN-1047 exposed queue metrics for the number of preempted containers to the
> fair scheduler. I would like to also expose these to the capacity scheduler
> and add metrics for the amount of lost memory seconds and vcore seconds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
