[
https://issues.apache.org/jira/browse/YARN-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402616#comment-15402616
]
Wangda Tan commented on YARN-5448:
----------------------------------
[~Naganarasimha],
bq. 1. This is one off wrong configuration scenario for this if we add
additional columns, then in general usage(after correction) its not of much use.
Sorry I may not quite sure about this. Could you explain?
bq. 2. Currently there are only two resources which are getting monitored (cpu
and memory), what about other resources which in future we want to add? so
adding multiple columns for each resource for this purpose doesn't seem good.
They're all legacy issues of existing UI, in the new UI it will be easier to
show:
a. For each resource type, we can show a pie chaart of (used / available /
non-usable), OR
b. Show vector of (used / available / non-usable).
I think a. should be more intuitive to me.
To be simple, we can only consider mem / vcores for now, adding to cols doesn't
sound like a problem to me.
bq. 3. Admin can immediately notice that there are some label which are
not-configured or part of cluster resource : Well its anyway related to
Scheduler page if admin sees a warning in parititon-by-queue-hierarchy chart
IMHO it should be sufficient.
To me it's not sufficient, we should have a way to show total resource of all
states (used / available-and-usable / non-usable) in a single place, which can
help answering questions like "why I cannot fully utilize the cluster".
bq. One other approach i could think of is instead of mentioning quantity of
total resource under each type(usable and unusable) how about number of
unusable(/ unallocatable) nodes ?
It's better to add a non-usable nodes as a separate col, but to me it may not a
fully replacement of total non-usable resources.
Thoughts?
> Resource in Cluster Metrics is not sum of resources in all nodes of all
> partitions
> ----------------------------------------------------------------------------------
>
> Key: YARN-5448
> URL: https://issues.apache.org/jira/browse/YARN-5448
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, resourcemanager, webapp
> Affects Versions: 2.7.2
> Reporter: Naganarasimha G R
> Assignee: Naganarasimha G R
> Attachments: NodesPage.png, schedulerPage.png
>
>
> Currently Resource info from Cluster Metrics are got from Queue Metrics's
> *available resource + allocated resource*. Hence if there are some nodes
> which belongs to partition but if that partition is not associated with any
> queue then in the capacity scheduler partition hierarchy shows this nodes
> resources under its partition but Cluster metrics doesn't show.
> Apart from this in the Nodes page too Metrics overview table is shown. So if
> we show Resource info from Queue Metrics User will not be able to co relate
> it. (have attached the images for the same)
> IIUC idea of not showing in the *Metrics overview table* is to highlight that
> configuration is not proper. This needs to be some how conveyed through
> parititon-by-queue-hierarchy chart.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
