[
https://issues.apache.org/jira/browse/HIVE-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496090#comment-16496090
]
Sankar Hariappan commented on HIVE-19340:
-----------------------------------------
[~ekoifman], [~sershe],
Currently, user/admin have the privilege to abort the replicated txn if they
need to kill it explicitly. Allowing timeout on replicated txn is not ideal as
several factors such as network delay, source cluster down, Beacon slow down
etc can cause timeout and this is indeterministic value.
Also, if the txn comes alive and committed at source but it is aborted in
target, and if committed txn is propagated to target, it will be ignored at
target causing loss of data. I think, this use-case should be handled by
replication.
cc [~maheshk114], [~thejas], [~anishek]
> 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)
