Member since
09-25-2015
356
Posts
382
Kudos Received
62
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1839 | 11-03-2017 09:16 PM | |
1456 | 10-17-2017 09:48 PM | |
2715 | 09-18-2017 08:33 PM | |
3024 | 08-04-2017 04:14 PM | |
2803 | 05-19-2017 06:53 AM |
06-24-2016
03:32 PM
2 Kudos
You should check the following: Make sure you are able to connect to the HiveServer2 through beeline, if not check the connection URL, In an unsecure cluster beeline session, the connection command is - !connect jdbc:hive2://<hostname>:10000/ <username> pwd If you are able to establish session, run simple commands like "show tables". This should succeed. Then proceed with the specific queries you want to run. If any of them fail, check the hiveserver2.log under hive log directories (typically /var/log/hive) under HIVE_HOST. If your query is failing on (2) can you please post the detailed error message from the hiveserver2 log.
... View more
06-14-2016
05:37 AM
1 Kudo
You should take a database dump of the various backend stores like Hive, Oozie, Ranger before the upgrade, see instructions here. This way after upgrade of MySQL if you run into issues you still have your backup database dumps.
... View more
06-09-2016
12:09 AM
2 Kudos
@William Bowen is disabling Atlas an acceptable workaround? To summarize the workaround, you disabled Atlas, modified hive config property "hive.exec.post.hooks" to get rid of "org.apache.atlas.hive.hook.HiveHook" from its value and then bounced the HiveServer2.
... View more
06-08-2016
10:36 PM
Can you post what is "hive.exec.post.hooks" in Hive configs set to? If it has the Atlas plugin in that list then remove that from the list and restart the HiveServer2.
... View more
06-08-2016
06:20 PM
Can you disable Atlas and see if the query works?
... View more
06-08-2016
06:17 PM
Its not the bad stats that cause this error. With the stats collected the cbo optimizer kicks in and somehow the optimized plan works.
... View more
06-03-2016
10:24 PM
2 Kudos
Easiest way to workaround this is to set hive.execution.engine to mr, this will make the query work but run slower. Other thing to try if you haven't done so is to do a stats collection on the tables involved. You can do it by: analyze table store_sales partition (...) compute statistics;
analyze table store_sales partition (...) compute statistics for columns;
And then enable hive.stats.fetch.column.stats if its not. Then run the query with tez execution engine.
... View more
06-03-2016
06:09 PM
1 Kudo
If you are using Ambari you can start the Spark ThriftServer by following the steps in the Spark documentation. Typically Ambari will setup the right configs under /etc/spark/conf. When you enable Spark ThriftServer it starts another service running as hive user.
... View more
05-23-2016
04:58 PM
1 Kudo
@Andrey Nikitin To debug this issue it's important to look at the HiveServer2 log. It goes into ${hive.log.dir}. You can search for this log location on the Ambari UI by searching for "log" under the Services > Hive > Configs, it should show up in the section "Advanced hive-env" and corresponds to field name "Hive Log Dir". Make sure that directory exists and writable by hive user. In this directory you will also find hivemetastore.log corresponding to Metastore service. The manual starting of HiveServer2 that you did /usr/bin/hive --service hiveserver2 was performed as root user, that is not going to work, the service needs to be started as "hive" user. When service is started manually, Ambari doesn't know about it and hence it will show as stopped. I think the way Ambari detects a running HiveServer2 service is by looking for a PID file that it put in the first place when it started HiveServer2. So, starting the service manually confuses Ambari and it shows it as not running. Typically when things are fine, running the following on hive host ps -ef | grep "^hive" should show two processes, one for Hive Metastore and other for HiveServer2.
... View more
03-28-2016
06:46 PM
That message indicates that your user password may have expired. However you should be able to run set commands SET PASSWORD = PASSWORD('new_updated_password');
After this your problem should go away.
... View more