Mapreduce jobs triggered from Talend ends up on the root.default queue even after passing the mapred.job.queue.name=root.amcb.medium

Highlighted
Four Stars

Mapreduce jobs triggered from Talend ends up on the root.default queue even after passing the mapred.job.queue.name=root.amcb.medium

Hello Team,

 

We are passing both 'spark.yarn.queue' and 'mapred.job.queue.name' with in the 'hive.execution.engine' parameter string.

All the Hive on Spark jobs land on the correct queue as expected.

However, All the Mapreduce task getting trigger by the particular Talend job ends up in the root.default queue !!

I have attached the screen shot for your reference, if you notice these are TestExportMapper.

 

It is critical for our environment to have all related task form a job to land on dedicated pool. 

Need you help on getting this sorted. 

 

Thanks in advance

Moderator

Re: Mapreduce jobs triggered from Talend ends up on the root.default queue even after passing the mapred.job.queue.name=root.amcb.medium

Hello,

We need more information w

Could you please create a support case on talend support portal? Our colleagues from support team will help you.

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 3

Read about some useful Context Variable ideas

Blog