[jira] [Commented] (YARN-5840) Yarn queues not being tracked correctly by Yarn Timeline
[ https://issues.apache.org/jira/browse/YARN-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15642949#comment-15642949 ] Weiwei Yang commented on YARN-5840: --- This should have been fixed in YARN-4044, marked as duplicated. > 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 > Fix For: 2.8.0, 3.0.0-alpha1 > > > 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
[jira] [Commented] (YARN-5840) Yarn queues not being tracked correctly by Yarn Timeline
[ https://issues.apache.org/jira/browse/YARN-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (YARN-5840) Yarn queues not being tracked correctly by Yarn Timeline
[ https://issues.apache.org/jira/browse/YARN-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15640854#comment-15640854 ] Weiwei Yang commented on YARN-5840: --- This issue was first found in 2.7.2, I had a patch for that. I will try reproduce this on trunk and see if it still an issue. Will upload a patch shortly if so. > 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
[jira] [Commented] (YARN-5840) Yarn queues not being tracked correctly by Yarn Timeline
[ https://issues.apache.org/jira/browse/YARN-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15640776#comment-15640776 ] ramtin commented on YARN-5840: -- Sure, I updated the description. > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5840) Yarn queues not being tracked correctly by Yarn Timeline
[ https://issues.apache.org/jira/browse/YARN-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15638534#comment-15638534 ] Naganarasimha G R commented on YARN-5840: - May be more description on what exactly you are looking forward to capture would be of good help ! > 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 > -- 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
