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-23560) Optimize bootstrap dump to abort only write Transactions
Date Mon, 20 Jul 2020 09:29:00 GMT


ASF GitHub Bot logged work on HIVE-23560:

                Author: ASF GitHub Bot
            Created on: 20/Jul/20 09:28
            Start Date: 20/Jul/20 09:28
    Worklog Time Spent: 10m 
      Work Description: pvary commented on a change in pull request #1232:

File path: standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift
@@ -2802,6 +2806,7 @@ PartitionsResponse get_partitions_req(1:PartitionsRequest req)
   void add_replication_metrics(1: ReplicationMetricList replicationMetricList) throws(1:MetaException
   ReplicationMetricList get_replication_metrics(1: GetReplicationMetricsRequest rqst) throws(1:MetaException
+  GetOpenTxnsResponse get_open_txns_req(1: GetOpenTxnsRequest getOpenTxnsRequest)

Review comment:
       Fair point

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: 460978)
    Time Spent: 3h  (was: 2h 50m)

> Optimize bootstrap dump to abort only write Transactions
> --------------------------------------------------------
>                 Key: HIVE-23560
>                 URL:
>             Project: Hive
>          Issue Type: Task
>            Reporter: Aasha Medhi
>            Assignee: Aasha Medhi
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-23560.01.patch, HIVE-23560.02.patch, HIVE-23560.03.patch, HIVE-23560.04.patch,
Optimize bootstrap dump to avoid aborting all transactions.pdf
>          Time Spent: 3h
>  Remaining Estimate: 0h
> Currently before doing a bootstrap dump, we abort all open transactions after waiting
for a configured time. We are proposing to abort only write transactions for the db under
replication and leave the read and repl created transactions as is.
> This doc attached talks about it in detail

This message was sent by Atlassian Jira

View raw message