[YARN-5840] Yarn queues not being tracked correctly by Yarn Timeline

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.7.2
• Assignee: Weiwei Yang
• Reporter: ramtin
• Created: 04/Nov/16 23:14
• Updated: 04/Jan/17 22:27
• Resolved: 07/Nov/16 03:12

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

Issue Links

• duplicates: YARN-4044 Running applications information changes such as movequeue is not published to TimeLine server