hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-23052) Optimize lock enqueueing in TxnHandler
Date Tue, 31 Mar 2020 10:45:00 GMT


Hive QA commented on HIVE-23052:

Here are the results of testing the latest attachment:

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

{color:green}SUCCESS:{color} +1 due to 18141 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: 12998260 - PreCommit-HIVE-Build

> Optimize lock enqueueing in TxnHandler
> --------------------------------------
>                 Key: HIVE-23052
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Marton Bod
>            Assignee: Marton Bod
>            Priority: Major
>         Attachments: HIVE-23052.1.patch, HIVE-23052.10.patch, HIVE-23052.2.patch, HIVE-23052.3.patch,
HIVE-23052.4.patch, HIVE-23052.5.patch, HIVE-23052.6.patch, HIVE-23052.7.patch, HIVE-23052.8.patch,
HIVE-23052.8.patch, HIVE-23052.8.patch, HIVE-23052.9.patch
> * Reduce scope of next_lock_id select-for-update by moving the txn_component inserts
before the S4U + inserting the hive_locks entries before the S4U (first with a temp ID, which
will be replaced later in a single update). This helps decrease the overall time that the
next_lock_id table is locked, thereby increasing concurrency
>  * Insert txn_components in a batch instead of one-by-one (also in TxnHandler::addDynamicPartition)
>  * Increment next_lock_id and update hive_locks table in a single batch statement

This message was sent by Atlassian Jira

View raw message