hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-10319) Hive CLI startup takes a long time with a large number of databases
Date Wed, 29 Jul 2015 20:32:06 GMT


Hive QA commented on HIVE-10319:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 9259 tests executed
*Failed tests:*
TestCliDriver-auto_join30.q-input10.q-join_reorder3.q-and-12-more - did not produce a TEST-*.xml

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed

This message is automatically generated.

ATTACHMENT ID: 12746748 - PreCommit-HIVE-TRUNK-Build

> Hive CLI startup takes a long time with a large number of databases
> -------------------------------------------------------------------
>                 Key: HIVE-10319
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: CLI
>    Affects Versions: 1.0.0
>            Reporter: Nezih Yigitbasi
>            Assignee: Nezih Yigitbasi
>         Attachments: HIVE-10319.1.patch, HIVE-10319.2.patch, HIVE-10319.3.patch, HIVE-10319.patch
> The Hive CLI takes a long time to start when there is a large number of databases in
the DW. I think the root cause is the way permanent UDFs are loaded from the metastore. When
I looked at the logs and the source code I see that at startup Hive first gets all the databases
from the metastore and then for each database it makes a metastore call to get the permanent
functions for that database [see |].
So the number of metastore calls made is in the order of the number of databases. In production
we have several hundreds of databases so Hive makes several hundreds of RPC calls during startup,
taking 30+ seconds.

This message was sent by Atlassian JIRA

View raw message