hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-21045) Add HMS total api count stats and connection pool stats to metrics
Date Fri, 25 Jan 2019 18:15:00 GMT


Hive QA commented on HIVE-21045:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 15719 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12956371 - PreCommit-HIVE-Build

> Add HMS total api count stats and connection pool stats to metrics
> ------------------------------------------------------------------
>                 Key: HIVE-21045
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Standalone Metastore
>            Reporter: Karthik Manamcheri
>            Assignee: Karthik Manamcheri
>            Priority: Minor
>         Attachments: HIVE-21045.1.patch, HIVE-21045.2.patch, HIVE-21045.3.patch, HIVE-21045.4.patch,
HIVE-21045.5.patch, HIVE-21045.6.patch, HIVE-21045.7.patch
> There are two key metrics which I think we lack and which would be really great to help
with scaling visibility in HMS.
> *Total API calls duration stats*
> We already compute and log the duration of API calls in the {{PerfLogger}}. We don't
have any gauge or timer on what the average duration of an API call is for the past some bucket
of time. This will give us an insight into if there is load on the server which is increasing
the average API response time.
> *Connection Pool stats*
> We can use different connection pooling libraries such as bonecp or hikaricp. These pool
managers expose statistics such as average time waiting to get a connection, number of connections
active, etc. We should expose this as a metric so that we can track if the the connection
pool size configured is too small and we are saturating!
> These metrics would help catch problems with HMS resource contention before they actually
have jobs failing.

This message was sent by Atlassian JIRA

View raw message