hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-19340) Disable timeout of transactions opened by replication task at target cluster
Date Tue, 16 Jun 2020 16:55:02 GMT


ASF GitHub Bot logged work on HIVE-19340:

                Author: ASF GitHub Bot
            Created on: 16/Jun/20 16:54
            Start Date: 16/Jun/20 16:54
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #337:

   This pull request has been automatically marked as stale because it has not had recent
activity. It will be closed if no further activity occurs.
   Feel free to reach out on the list if the patch is in need of reviews.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

            Worklog Id:     (was: 446694)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 3.1.0, 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,
>          Time Spent: 10m
>  Remaining Estimate: 0h
> 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