[
https://issues.apache.org/jira/browse/HIVE-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494559#comment-16494559
]
mahesh kumar behera commented on HIVE-19340:
--------------------------------------------
[~sershe] [~ekoifman] [~thejas] [~sankarh]
Sorry i did'nt update here the discussion we had with Eugene.
# We should not allow user to abort it as its created by replication task.
# Only admin/super user should be able to abort these transaction.
# In fact we need to have some authorization mechanism to validate user
aborting any transaction.
# I have created a internal Jira
([BUG-102193|https://hortonworks.jira.com/browse/BUG-102193]) to address the
abort transaction for tracking.
> 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)
