Quanlong Huang created IMPALA-14152:
---------------------------------------
Summary: HMS 3.1.3 in test env is not functional
Key: IMPALA-14152
URL: https://issues.apache.org/jira/browse/IMPALA-14152
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Reporter: Quanlong Huang
Assignee: Quanlong Huang
Tried loading testdata on a build of Apache components that uses Apache Hive
3.1.3. Saw this failure:
{noformat}
Running warm up Hive statements
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/home/ubuntu/Impala/toolchain/apache_components/apache-hive-3.1.3-bin/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/home/ubuntu/Impala/toolchain/apache_components/hadoop-3.4.1/share/hadoop/common/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
Connecting to jdbc:hive2://localhost:11050/default;
Connected to: Apache Hive (version 3.1.3)
Driver: Hive JDBC (version 3.1.3)
Transaction isolation: TRANSACTION_REPEATABLE_READ
Error: Error while compiling statement: FAILED: LockException [Error 10280]:
Error communicating with the metastore (state=42000,code=10280){noformat}
Checking HMS logs, there are lots of exceptions due to this:
{code}
Caused by: java.lang.RuntimeException: Property p.connectionTimeout does not
exist on target class com.zaxxer.hikari.HikariConfig{code}
An example stacktrace:
{code}
2025-06-15T15:00:06,237 ERROR [Metastore threads starter thread]
util.PropertyElf: Property p.connectionTimeout does not exist on target class
com.zaxxer.hikari.HikariConfig
2025-06-15T15:00:06,237 ERROR [Metastore threads starter thread]
txn.TxnHandler: Unable to instantiate JDBC connection pooling
java.sql.SQLException: Cannot create HikariCP configuration:
at
org.apache.hadoop.hive.metastore.datasource.HikariCPDataSourceProvider.create(HikariCPDataSourceProvider.java:59)
~[hive-exec-3.1.3.jar:3.1.3]
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.setupJdbcConnectionPool(TxnHandler.java:4519)
[hive-exec-3.1.3.jar:3.1.3]
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.setConf(TxnHandler.java:301)
[hive-exec-3.1.3.jar:3.1.3]
at
org.apache.hadoop.hive.metastore.txn.TxnUtils.getTxnStore(TxnUtils.java:202)
[hive-exec-3.1.3.jar:3.1.3]
at
org.apache.hadoop.hive.ql.txn.compactor.CompactorThread.init(CompactorThread.java:92)
[hive-exec-3.1.3.jar:3.1.3]
at org.apache.hadoop.hive.ql.txn.compactor.Worker.init(Worker.java:221)
[hive-exec-3.1.3.jar:3.1.3]
at
org.apache.hadoop.hive.metastore.HiveMetaStore.initializeAndStartThread(HiveMetaStore.java:9216)
[hive-exec-3.1.3.jar:3.1.3]
at
org.apache.hadoop.hive.metastore.HiveMetaStore.startCompactorWorkers(HiveMetaStore.java:9185)
[hive-exec-3.1.3.jar:3.1.3]
at
org.apache.hadoop.hive.metastore.HiveMetaStore.access$1500(HiveMetaStore.java:199)
[hive-exec-3.1.3.jar:3.1.3]
at
org.apache.hadoop.hive.metastore.HiveMetaStore$3.run(HiveMetaStore.java:9145)
[hive-exec-3.1.3.jar:3.1.3]
Caused by: java.lang.RuntimeException: Property p.connectionTimeout does not
exist on target class com.zaxxer.hikari.HikariConfig
at com.zaxxer.hikari.util.PropertyElf.setProperty(PropertyElf.java:131)
~[HikariCP-2.6.1.jar:?]
at
com.zaxxer.hikari.util.PropertyElf.lambda$setTargetFromProperties$0(PropertyElf.java:57)
~[HikariCP-2.6.1.jar:?]
at java.util.Hashtable.forEach(Hashtable.java:879) ~[?:1.8.0_452]
at
com.zaxxer.hikari.util.PropertyElf.setTargetFromProperties(PropertyElf.java:52)
~[HikariCP-2.6.1.jar:?]
at com.zaxxer.hikari.HikariConfig.<init>(HikariConfig.java:130)
~[HikariCP-2.6.1.jar:?]
at
org.apache.hadoop.hive.metastore.datasource.HikariCPDataSourceProvider.create(HikariCPDataSourceProvider.java:57)
~[hive-exec-3.1.3.jar:3.1.3]
... 9 more{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
