Member since
12-11-2015
67
Posts
10
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2531 | 05-11-2016 04:36 PM | |
3200 | 01-28-2016 10:42 PM |
02-09-2016
08:50 PM
1 Kudo
Hi, Could you please let me know where is this amb_ranger_admin user name is stored? (Ambari/Ranger databases)?
... View more
01-28-2016
10:42 PM
1 Kudo
I tried to manually start/stop from problematic node and it was very quick. Below are the commands used /usr/hdp/current/hbase-regionserver/bin/hbase-daemon.sh --config /usr/hdp/current/hbase-regionserver/conf start/stop regionserver When the regionserver stopped manually, Ambari is notified about the change and reduced the no of regionserver count and increased the count when started the regionserver manually.
So, it is confirmed that the problem is only when starting/stopping from the Ambari but no logs related to the delay either in ambar-server.log or in ambari-agent.logs
... View more
01-28-2016
08:47 PM
I checked in server and agent logs but I did not see anything when I invoked the start/stop from Ambari from the problematic server
... View more
01-28-2016
07:17 PM
1 Kudo
Hi, We have a cluster of 10 servers. One worker server among them has the problem while starting/stopping services from Ambari. When I try to invoke any operations on any service (HDFS/HBASE/METRICS) from Ambari, the command is taking very long time to execute. I searched Ambari logs, Servcie logs but could not find any error. I tried to restart Ambari server and Ambari agent but still no luck. I had the same problem earlier but reinstalling ambari-agent fixed the issue but no luck now. I deleted host from cluster, cleaned total server and added back to server but still the same issue. Please advice. Thanks, Venkat
... View more
Labels:
- Labels:
-
Apache Ambari
01-27-2016
10:08 PM
Hi, Ranger usersync process not synching the AD users and throwing below error when a new user is added 27 Jan 2016 15:48:15 ERROR LdapUserGroupBuilder [UnixUserSyncThread] - sink.addOrUpdateUser failed with exception: POST https://server1:6182/service/users/default returned a response status of 403 Forbidden, for user: mthal, groups: It has picked the newly added user but could not add it to ranger users list. I have enabled the SSL for Ranger. Please advice Thanks, Venkat
... View more
Labels:
- Labels:
-
Apache Ranger
01-22-2016
08:53 PM
Yes..!! It solved the problem
... View more
01-22-2016
08:50 PM
Done and it addressed the problem. I somehow missed it but thanks once again Artem Ervits..!!
... View more
01-22-2016
08:16 PM
1 Kudo
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?
... View more
01-22-2016
08:14 PM
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
... View more
Labels:
- Labels:
-
Apache Hive
01-15-2016
04:31 PM
1 Kudo
Hey Emaxwell, You are correct. The args should be after the configuration block is closed. The workflow is valid now Artem Ervits: Thank you so much for your help on this. The issue is resolved..!!
... View more