[
https://issues.apache.org/jira/browse/YARN-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174082#comment-15174082
]
Sunil G commented on YARN-4634:
-------------------------------
Thanks [~leftnoteasy] for the comments.
I agree that we are considering too many variables to decide upon whether to
render with labels or not in earlier patch. Yes, it adds the complexity.
Meantime, current system has some corner cases where label-queue mappings are
not present too. So i think such cases can be handled by assuming that we
render UI with labels.
So I will try to consolidate the idea here, if cluster has labels other than
DEFAULT_LABEL and at least one such label has >0 active NMs (other than
DEFAULT_LABEL), then we will render UI with labels. Is this fine?
> Scheduler UI/Metrics need to consider cases like non-queue label mappings
> -------------------------------------------------------------------------
>
> Key: YARN-4634
> URL: https://issues.apache.org/jira/browse/YARN-4634
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.7.1
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-YARN-4634.patch, 0002-YARN-4634.patch
>
>
> Currently when label-queue mappings are not available, there are few
> assumptions taken in UI and in metrics.
> In above case where labels are enabled and available in cluster but without
> any queue mappings, UI displays queues under labels. This is not correct.
> Currently labels enabled check and availability of labels are considered to
> render scheduler UI. Henceforth we also need to check whether
> - queue-mappings are available
> - nodes are mapped with labels with proper exclusivity flags on
> This ticket also will try to see the default configurations in queue when
> labels are not mapped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
