hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-10925) Non-static threadlocals in metastore code can potentially cause memory leak
Date Thu, 04 Jun 2015 14:46:38 GMT


Hive QA commented on HIVE-10925:

{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 3 failed/errored test(s), 8998 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: 3 tests failed

This message is automatically generated.

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

> Non-static threadlocals in metastore code can potentially cause memory leak
> ---------------------------------------------------------------------------
>                 Key: HIVE-10925
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.14.0, 1.0.0, 1.2.0, 1.1.0, 0.13
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>         Attachments: HIVE-10925.1.patch
> There are many places where non-static threadlocals are used. I can't seem to find a
good logic for using them. However, they can potentially result in leaking objects if for
example they are created in a long running thread every time the thread handles a new session.

This message was sent by Atlassian JIRA

View raw message