hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramtin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5840) Yarn queues not being tracked correctly by Yarn Timeline
Date Sat, 05 Nov 2016 23:39:58 GMT

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

ramtin updated YARN-5840:
-------------------------
    Description: 
By creating Yarn sub-queues and mapping users/groups to these sub-queues when the Job runs
the Yarn client seems to capture the correct queue for that Job but if you go to the Yarn
Timeline Server to see these jobs, they all get tagged to the "default" queue.
This makes it hard for easily map the cluster consumption by different departments which belong
to different users

>  Yarn queues not being tracked correctly by Yarn Timeline
> ---------------------------------------------------------
>
>                 Key: YARN-5840
>                 URL: https://issues.apache.org/jira/browse/YARN-5840
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: ramtin
>            Assignee: Weiwei Yang
>            Priority: Minor
>
> By creating Yarn sub-queues and mapping users/groups to these sub-queues when the Job
runs the Yarn client seems to capture the correct queue for that Job but if you go to the
Yarn Timeline Server to see these jobs, they all get tagged to the "default" queue.
> This makes it hard for easily map the cluster consumption by different departments which
belong to different users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message