Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 06-01-2016 01:13 PM
I am running a query which runs 52 map jobs simultaneously. Due to this my Resource manager container gets filled up completely and consumed up 100%. The query stucks at that point and giving no result.
I want to reduce number of map tasks which runs in parallel.
Created 06-01-2016 01:26 PM
You will have to pass runtime parameters to Hive query.
See this post.
Created 06-01-2016 01:26 PM
You will have to pass runtime parameters to Hive query.
See this post.
Created 06-01-2016 02:15 PM
@Tajinderpal Singh Also, look at mapreduce.job.reduce.slowstart.completedmaps properties in map-reduce and set this to 0.9. This property will ensure reducers not coming in early and waiting for mappers to complete there by avoiding hung jobs.
Created 06-01-2016 06:43 PM
You can set the run time parameters within hive shell, or pass them through your script, as mentioned by Pranay. Also if you are using Tez, this particular article on how to tune the performance may come in Handy.