hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-21103) PartitionManagementTask should not modify DN configs to avoid closing persistence manager
Date Thu, 07 Feb 2019 03:06:00 GMT


Hive QA commented on HIVE-21103:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 15777 tests executed
*Failed tests:*

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
Tests exited with: TestsFailedException: 1 tests failed

This message is automatically generated.

ATTACHMENT ID: 12957834 - PreCommit-HIVE-Build

> PartitionManagementTask should not modify DN configs to avoid closing persistence manager
> -----------------------------------------------------------------------------------------
>                 Key: HIVE-21103
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Standalone Metastore
>    Affects Versions: 4.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Critical
>         Attachments: HIVE-21103.1.patch, HIVE-21103.2.patch, HIVE-21103.3.patch
> HIVE-20707 added automatic partition management which uses thread pools to run parallel
msck repair. It also modifies datanucleus connection pool size to avoid explosion of connections
to backend database. But object store closes the persistence manager when it detects a change
in datanuclues or jdo configs. So when PartitionManagementTask is running and when HS2 tries
to connect to metastore HS2 will get persistence manager close exception. 

This message was sent by Atlassian JIRA

View raw message