[
https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662391#comment-14662391
]
Siqi Li commented on YARN-3176:
-------------------------------
>From FairSchedulerPage, it looks like the UI has already handle the
>Integer.MAX_VALUE case.
{code}
protected void render(Block html) {
ResponseInfo ri = info("\'" + qinfo.getQueueName() + "\' Queue Status").
_("Used Resources:", qinfo.getUsedResources().toString()).
_("Num Active Applications:", qinfo.getNumActiveApplications()).
_("Num Pending Applications:", qinfo.getNumPendingApplications()).
_("Min Resources:", qinfo.getMinResources().toString()).
_("Max Resources:", qinfo.getMaxResources().toString());
int maxApps = qinfo.getMaxApplications();
if (maxApps < Integer.MAX_VALUE) {
ri._("Max Running Applications:", qinfo.getMaxApplications());
}
ri._(STEADY_FAIR_SHARE + ":", qinfo.getSteadyFairShare().toString());
ri._(INSTANTANEOUS_FAIR_SHARE + ":", qinfo.getFairShare().toString());
html._(InfoBlock.class);
// clear the info contents so this queue's info doesn't accumulate into
another queue's info
ri.clear();
}
{code}
I think the best way to fix the UI is also displaying the information(i.e.
Queue status box) for parent queue. By doing this, there will be no more
confusion
> In Fair Scheduler, child queue should inherit maxApp from its parent
> --------------------------------------------------------------------
>
> Key: YARN-3176
> URL: https://issues.apache.org/jira/browse/YARN-3176
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Siqi Li
> Assignee: Siqi Li
> Attachments: YARN-3176.v1.patch, YARN-3176.v2.patch
>
>
> if the child queue does not have a maxRunningApp limit, it will use the
> queueMaxAppsDefault. This behavior is not quite right, since
> queueMaxAppsDefault is normally a small number, whereas some parent queues do
> have maxRunningApp set to be more than the default
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
