I was trying to benchmark some hive queries. I am using the tez execution engine. I varied the values of the following properties:
Changes in values for property 1 is reflected properly. However it seems that hive does not respect changes in values of property 3; it always allocates one vcore per requested container (RM is configured to use the DominantResourceCalculator). This got me thinking about the precedence of property values in hive and tez.
I have the following questions with respect to these configurations
1. Does hive respect the set values for the properties 2 and 3 at all?
2. If I set property 1 to a value say 2048 MB and property 2 is set to a value of say 1024 MB does this mean that I am wasting about a GB of memory for each spawned container?
3. Is there a property in hive similar to property 1 that allows me to use the 'set' command in the .hql file to specify the number of vcores to use per container?
4. Changes in value for the property tez.am.resource.cpu.vcores are reflected at runtime. However I do not observe the same behaviour with property 3. Are there other configurations that take precedence over it?
Your inputs and suggestions would be highly appreciated.
To be clear, this means that there is no way to control the number of 'vcores' for every task container requested by the application master. The only valid configuration (for task containers) would be hive.tez.container.size, which again should be set accordingly so as to ensure that every spawned container on a particular m/c has access to EXACTLY ONE vcore on that m/c.
Please correct me if I'm wrong in understanding this.
Tez tasks are mostly single threaded. Parallelization is achieved by tasks. So increasing the cores will not help you.
I would suppose so. Also he is working with the timeline server, communicating with the Resourcemanager and nodemanagers does logging, etc.