hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-9199) Excessive exclusive lock used in some DDLs with DummyTxnManager
Date Wed, 24 Dec 2014 03:29:14 GMT


Hive QA commented on HIVE-9199:

{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), 6722 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: 12688897 - PreCommit-HIVE-TRUNK-Build

> Excessive exclusive lock used in some DDLs with DummyTxnManager
> ---------------------------------------------------------------
>                 Key: HIVE-9199
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking
>            Reporter: Chaoyu Tang
>            Assignee: Chaoyu Tang
>         Attachments: HIVE-9199.patch
> In DummyTxnManager, the lockMode for a WriteEntity (e.g. database, table) is determined
by "complete" instead of its writeType. But since DDL output WriteEntity is usually complete,
some DDL operations might be given exclusive locks which are actually not needed, which causes
unnecessary locking contention. For example, in createTable, DummyTxnManager suggests an exclusive
lock to table database writeentity since it is complete.

This message was sent by Atlassian JIRA

View raw message