hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-19340) Disable timeout of transactions opened by replication task at target cluster
Date Fri, 15 Jun 2018 00:37:00 GMT


Hive QA commented on HIVE-19340:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 14456 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestMiniDruidCliDriver.testCliDriver[druidkafkamini_basic] (batchId=254)
org.apache.hadoop.hive.ql.TestTxnCommands2.testMultiInsertStatement (batchId=287)
org.apache.hive.spark.client.rpc.TestRpc.testServerPort (batchId=306)

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

This message is automatically generated.

ATTACHMENT ID: 12927674 - PreCommit-HIVE-Build

> Disable timeout of transactions opened by replication task at target cluster
> ----------------------------------------------------------------------------
>                 Key: HIVE-19340
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl, Transactions
>    Affects Versions: 3.0.0
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: ACID, DR, pull-request-available, replication
>             Fix For: 4.0.0
>         Attachments: HIVE-19340.01.patch, HIVE-19340.02.patch, HIVE-19340.03-branch-3.patch,
HIVE-19340.03.patch, HIVE-19340.04-branch-3.patch, HIVE-19340.06-branch-3.patch, HIVE-19340.06.patch,
> The transactions opened by applying EVENT_OPEN_TXN should never be aborted automatically
due to time-out. Aborting of transaction started by replication task may leads to inconsistent
state at target which needs additional overhead to clean-up. So, it is proposed to mark the
transactions opened by replication task as special ones and shouldn't be aborted if heart
beat is lost. This helps to ensure all ABORT and COMMIT events will always find the corresponding
txn at target to operate.

This message was sent by Atlassian JIRA

View raw message