[jira] [Created] (HIVE-22871) Show info message in log when hive server return response with success status with info
Shaohui Liu created HIVE-22871: -- Summary: Show info message in log when hive server return response with success status with info Key: HIVE-22871 URL: https://issues.apache.org/jira/browse/HIVE-22871 Project: Hive Issue Type: Improvement Reporter: Shaohui Liu Assignee: Shaohui Liu The info messages in TStatus of HiveServer response are very useful to debug the SQL executions. Currently, the info messages are ignored when getting TStatus: SUCCESS or SUCCESS_WITH_INFO_STATUS. It‘s better to show these info messages in LOG when receiving SUCCESS or SUCCESS_WITH_INFO_STATUS TStatus. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-22837) Make opertion log delay cleanup work for all operations
Shaohui Liu created HIVE-22837:
--
Summary: Make opertion log delay cleanup work for all operations
Key: HIVE-22837
URL: https://issues.apache.org/jira/browse/HIVE-22837
Project: Hive
Issue Type: Improvement
Affects Versions: 3.1.2
Reporter: Shaohui Liu
Assignee: Shaohui Liu
Currently, the operation log delay cleanup work only when a query is cancelled.
It's a very useful feature to debug the SQL through the operation log.
I think it should be enabled for all operations
{code:java}
2020-02-06T13:30:03,537 INFO [f5a6a379-09f6-4fd8-8f1f-25034eee0ff8
HiveServer2-Handler-Pool: Thread-76] operation.Operation: Closing operation log
./operationlog/f5a6a379-09f6-4fd8-8f1f-25034eee0ff8/work_20200206133003_580d028f-0ca0-4fd6-9cc4-e56b57c29439
without delay
2020-02-06T13:30:03,537 INFO [d3f09003-5507-4dbe-a900-69f245c41fae
HiveServer2-Handler-Pool: Thread-77] operation.Operation: Closing operation log
./operationlog/d3f09003-5507-4dbe-a900-69f245c41fae/work_20200206133003_5b6b405d-c0ed-4b44-aee1-d4dd4b57f8a2
without delay
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HIVE-22836) HiveServer2 sttart failed for tez ClassNotFoundException
Shaohui Liu created HIVE-22836:
--
Summary: HiveServer2 sttart failed for tez ClassNotFoundException
Key: HIVE-22836
URL: https://issues.apache.org/jira/browse/HIVE-22836
Project: Hive
Issue Type: Bug
Affects Versions: 3.1.2
Reporter: Shaohui Liu
Assignee: Shaohui Liu
{code:java}
2020-02-05 21:36:54 [main] INFO HiveServer2:877 - Stopping/Disconnecting tez
sessions.
2020-02-05 21:36:54 [main] INFO HiveServer2:883 - Stopped tez session pool
manager.
2020-02-05 21:36:54 [main] ERROR HiveServer2:1307 - Error starting HiveServer2
java.lang.Error: Max start attempts 1 exhausted
at
org.apache.hive.service.server.HiveServer2.startHiveServer2(HiveServer2.java:1062)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.access$1600(HiveServer2.java:140)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2$StartOptionExecutor.execute(HiveServer2.java:1305)
[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.main(HiveServer2.java:1149)
[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
Caused by: java.lang.NoClassDefFoundError:
org/apache/tez/dag/api/SessionNotRunning
at
org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolSession$AbstractTriggerValidator.startTriggerValidator(TezSessionPoolSession.java:74)
~[hive-exec-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolManager.initTriggers(TezSessionPoolManager.java:207)
~[hive-exec-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolManager.startPool(TezSessionPoolManager.java:114)
~[hive-exec-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.initAndStartTezSessionPoolManager(HiveServer2.java:839)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.startOrReconnectTezSessions(HiveServer2.java:822)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.start(HiveServer2.java:745)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.startHiveServer2(HiveServer2.java:1037)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
... 3 more
Caused by: java.lang.ClassNotFoundException:
org.apache.tez.dag.api.SessionNotRunning
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
~[?:1.8.0_202]
at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_202]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
~[?:1.8.0_202]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_202]
at
org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolSession$AbstractTriggerValidator.startTriggerValidator(TezSessionPoolSession.java:74)
~[hive-exec-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolManager.initTriggers(TezSessionPoolManager.java:207)
~[hive-exec-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolManager.startPool(TezSessionPoolManager.java:114)
~[hive-exec-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.initAndStartTezSessionPoolManager(HiveServer2.java:839)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.startOrReconnectTezSessions(HiveServer2.java:822)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.start(HiveServer2.java:745)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
at
org.apache.hive.service.server.HiveServer2.startHiveServer2(HiveServer2.java:1037)
~[hive-service-3.1.2-mdh3.1.2.0-SNAPSHOT.jar:3.1.2-mdh3.1.2.0-SNAPSHOT]
... 3 more
{code}
In our use case, TEZ engine is not used. Maybe we can add a conf to disable
tez execution enigine.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
