Random UUIDs Are Used as Task Names During Tez Task Sampling

Symptom

When a Hive Tez session fails to be executed and a new session is started, a random UUID is generated as the new session name. In this case, the UUID is resolved into an application name. Because identification_type is set to the same value of application_name and the random UUID differs from the original application name, parameters in best_config cannot be updated during sampling and exceptions occur as shown in the following figure:

1
2
3
4

7a4f4be0-7bed-4102-ae09-a6345ee43cce
8ff36712-8c66-4544-abff-b9751e607cf7
cdd26108-3fbd-4f1b-af98-89d7964083f6
e8b3ccbe-b043-465f-b0b0-e01297ef658d

Key Process and Cause Analysis

None

Conclusion and Solution

1. Open the $HIVE_HOME/conf/hive-site.xml configuration file.

   vi $HIVE_HOME/conf/hive-site.xml

2. Press i to enter the insert mode and add the following content to the end of the file:

   1 2 3 4 5 6 7 8

   <property> <name>hive.cli.tez.session.async</name> <value>false</value> <description> Whether to start Tez session in background when running CLI with Tez, allowing CLI to be available earlier. </description> </property>

3. Press Esc, type :wq!, and press Enter to save the file and exit.
4. Perform parameter sampling again by following instructions in Using OmniAdvisor in the OmniRuntime Feature Guide.