[
https://issues.apache.org/jira/browse/HIVE-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494615#comment-16494615
]
mahesh kumar behera commented on HIVE-19340:
--------------------------------------------
Currently replication code can not handle if user aborts the transaction.
There can be data inconsistencies if user does a load after aborting the
transaction. So we decided to allow admin to abort the transaction if it’s
sure that there will not be any load afterwards.
On Wed, 30 May 2018 at 7:00 AM, Sergey Shelukhin (JIRA) <[email protected]>
> 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: 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
>
>
> 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)
