Accessing Hive cli is hung forever with java.sql.SQLException

venkata_gangava — Fri, 16 Sep 2022 09:59:09 GMT

Hi,

I could not access Hive CLI with below error messages

16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: Overriding datanucleus.identifierFactory value null from jpox.properties with datanucleus1 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: Overriding javax.jdo.option.ConnectionURL value null from jpox.properties with jdbc:derby:;databaseName=/var/lib/hive/metastore/metastore_db;create=true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: Overriding javax.jdo.option.DetachAllOnCommit value null from jpox.properties with true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: Overriding hive.metastore.integral.jdo.pushdown value null from jpox.properties with false 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: Overriding datanucleus.storeManagerType value null from jpox.properties with rdbms 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: Overriding datanucleus.transactionIsolation value null from jpox.properties with read-committed 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: Overriding javax.jdo.PersistenceManagerFactoryClass value null from jpox.properties with org.datanucleus.api.jdo.JDOPersistenceManagerFactory 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: Overriding javax.jdo.option.Multithreaded value null from jpox.properties with true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.rdbms.useLegacyNativeValueStrategy = true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: hive.metastore.integral.jdo.pushdown = false 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.autoStartMechanismMode = checked 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: javax.jdo.option.Multithreaded = true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.identifierFactory = datanucleus1 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.transactionIsolation = read-committed 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.validateTables = false 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: javax.jdo.option.ConnectionURL = jdbc:derby:;databaseName=/var/lib/hive/metastore/metastore_db;create=true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: javax.jdo.option.DetachAllOnCommit = true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: javax.jdo.option.NonTransactionalRead = true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.fixedDatastore = false 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.validateConstraints = false 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: javax.jdo.option.ConnectionDriverName = org.apache.derby.jdbc.EmbeddedDriver 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: javax.jdo.option.ConnectionUserName = APP 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.validateColumns = false 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.cache.level2 = false 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.plugin.pluginRegistryBundleCheck = LOG 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.cache.level2.type = none 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: javax.jdo.PersistenceManagerFactoryClass = org.datanucleus.api.jdo.JDOPersistenceManagerFactory 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.autoCreateSchema = true 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.storeManagerType = rdbms 16/01/22 12:59:03 [main]: DEBUG metastore.ObjectStore: datanucleus.connectionPoolingType = BONECP 16/01/22 12:59:03 [main]: INFO metastore.ObjectStore: ObjectStore, initialize called 16/01/22 12:59:04 [main]: DEBUG bonecp.BoneCPDataSource: JDBC URL = jdbc:derby:;databaseName=/var/lib/hive/metastore/metastore_db;create=true, Username = APP, partitions = 1, max (per partition) = 10, min (per partition) = 0, idle max age = 60 min, idle test period = 240 min, strategy = DEFAULT 16/01/22 12:59:04 [BoneCP-pool-watch-thread]: ERROR bonecp.PoolWatchThread: Error in trying to obtain a connection. Retrying in 7000ms java.sql.SQLException: A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setReadOnly(Unknown Source) at com.jolbox.bonecp.ConnectionHandle.setReadOnly(ConnectionHandle.java:1324) at com.jolbox.bonecp.ConnectionHandle.<init>(ConnectionHandle.java:262) at com.jolbox.bonecp.PoolWatchThread.fillConnections(PoolWatchThread.java:115) at com.jolbox.bonecp.PoolWatchThread.run(PoolWatchThread.java:82) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.sql.SQLException: A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 13 more Caused by: ERROR 25505: A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection.

We are using Mysql for metastore but I see JDBC URl with Derby database. I am not sure if it can be ignored but highlighting if it gives any hint about the issue.

Please help

Re: Accessing Hive cli is hung forever with java.sql.SQLException

venkata_gangava — Sat, 23 Jan 2016 04:16:31 GMT

Hey, I found the root cause for the problem. hive-site.xml file is not getting updated by Ambari for some reason but it is updated on another server where hive client is installed. I have copied the file to server where Hive master servcies are running and it works fine now.

Now, another problem. Why is Ambari not updating the hive-site.xml file on master server?

Re: Accessing Hive cli is hung forever with java.sql.SQLException

aervits — Sat, 23 Jan 2016 04:25:59 GMT

@Venkata Sridhar Gangavarapu

go to the problematic node and install hive client via Ambari.

Re: Accessing Hive cli is hung forever with java.sql.SQLException

venkata_gangava — Sat, 23 Jan 2016 04:50:45 GMT

Done and it addressed the problem. I somehow missed it but thanks once again Artem Ervits..!!

Re: Accessing Hive cli is hung forever with java.sql.SQLException

aervits — Sat, 23 Jan 2016 04:51:11 GMT

adding the client fixed the problem? @Venkata Sridhar Gangavarapu

Re: Accessing Hive cli is hung forever with java.sql.SQLException

venkata_gangava — Sat, 23 Jan 2016 04:53:27 GMT

Yes..!!

It solved the problem

question Re: Accessing Hive cli is hung forever with java.sql.SQLException in Archives of Support Questions (Read Only)

Accessing Hive cli is hung forever with java.sql.SQLException

Re: Accessing Hive cli is hung forever with java.sql.SQLException

Re: Accessing Hive cli is hung forever with java.sql.SQLException

Re: Accessing Hive cli is hung forever with java.sql.SQLException

Re: Accessing Hive cli is hung forever with java.sql.SQLException

Re: Accessing Hive cli is hung forever with java.sql.SQLException