[ https://issues.apache.org/jira/browse/YARN-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15641945#comment-15641945 ]
Naganarasimha G R commented on YARN-5840: ----------------------------------------- Hi [~cheersyang] & [~ramtinb], My guess is, its already got solved in the trunk/2.7.3 code. Can you once check with it ? > 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 > Affects Versions: 2.7.2 > Reporter: ramtin > Assignee: Weiwei Yang > > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org