hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-9870) Add JvmPauseMonitor threads to HMS and HS2 daemons
Date Thu, 05 Mar 2015 16:54:38 GMT


Hive QA commented on HIVE-9870:

{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 1 failed/errored test(s), 7599 tests executed
*Failed tests:*

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: 1 tests failed

This message is automatically generated.

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

> Add JvmPauseMonitor threads to HMS and HS2 daemons
> --------------------------------------------------
>                 Key: HIVE-9870
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2, Metastore
>    Affects Versions: 1.1
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>         Attachments: HIVE-9870.patch
> The hadoop-common carries in it a nifty thread that prints GC or non-GC pauses within
the JVM if it exceeds a specific threshold.
> This has been immeasurably useful in supporting several clusters, in identifying GC or
other form of process pauses to be the root cause of some event being investigated.
> The HMS and HS2 daemons are good targets for running similar threads within it. It can
be loaded in an if-available style.

This message was sent by Atlassian JIRA

View raw message