Re: Any HIVE DDL statement takes minutes to execute

How about disable kerberos and give a try? The time cost looks like waiting for something to timeout, for example DNS reverse lookup. From: Alan Gates Sent: Friday, May 17, 2019 8:05:04 AM To: user@hive.apache.org Subject: Re: Any HIVE DDL statement takes

Re: Any HIVE DDL statement takes minutes to execute

I can think of two things that could take a long time in creating a table, database operations or file system operations. The perf timers inside the metastore only measure the entire metadata operation, not the file part and the db part, so it will be hard to tell where the time is being spent.

HS2 for v2.3.4 takes a long time to start

Hi, We are migrating from Hive 2.0.1 to 2.3.4. In the test environment, we have cloned data from the production hive metastore which has about 100 databases and each database has about 300 tables. When we are starting the thrift server using *hive --server hiveserver2, *it takes a long time for

RE: Any HIVE DDL statement takes minutes to execute

Hi Mich, First thank you for taking the time to look over this problem. Now regarding the questions : 1. I can confirm there are no locks on metastore DB ; 2. About duration of the queries, in my previous mail I just gave some examples and I can confirm that I run those queries on the

Re: Any HIVE DDL statement takes minutes to execute

Dr Mich Talebzadeh LinkedIn * https://www.linkedin.com/profile/view?id=AAEWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw * http://talebzadehmich.wordpress.com *Disclaimer:* Use it at your own risk. Any and all

RE: Any HIVE DDL statement takes minutes to execute

Hi Alan, I’m using MySQL (Mariadb) for the metastore and I was thinking on this possibility too but from all my tests on metastore database that I run, every query is almost instant. For example : SELECT * FROM `TBLS` -> Query took 0.0001 seconds. INSERT INTO `TBLS` -> Query took 0.0020