[
https://issues.apache.org/jira/browse/HIVE-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16455740#comment-16455740
]
ASF GitHub Bot commented on HIVE-19340:
---------------------------------------
GitHub user maheshk114 opened a pull request:
https://github.com/apache/hive/pull/337
HIVE-19340 : Disable timeout of transactions opened by replication ta…
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/maheshk114/hive BUG-92700
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/337.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #337
----
commit 317d29c8455ad8aaccf1689c66d79f7bab41cde7
Author: Mahesh Kumar Behera <mbehera@...>
Date: 2018-04-27T03:24:08Z
HIVE-19340 : Disable timeout of transactions opened by replication task at
target cluster
----
> Disable timeout of transactions opened by replication task at target cluster
> ----------------------------------------------------------------------------
>
> Key: HIVE-19340
> URL: https://issues.apache.org/jira/browse/HIVE-19340
> 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: 3.0.0
>
> Attachments: HIVE-19340.01.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
(v7.6.3#76005)
