[ 
https://issues.apache.org/jira/browse/HIVE-24909?focusedWorklogId=578031&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-578031
 ]

ASF GitHub Bot logged work on HIVE-24909:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Apr/21 00:20
            Start Date: 07/Apr/21 00:20
    Worklog Time Spent: 10m 
      Work Description: hmangla98 commented on a change in pull request #2101:
URL: https://github.com/apache/hive/pull/2101#discussion_r608259119



##########
File path: ql/src/java/org/apache/hadoop/hive/ql/lockmgr/DbTxnManager.java
##########
@@ -170,6 +170,7 @@ Licensed to the Apache Software Foundation (ASF) under one
   private ScheduledFuture<?> heartbeatTask = null;
   private static final int SHUTDOWN_HOOK_PRIORITY = 0;
   private final ReentrantLock heartbeatTaskLock = new ReentrantLock();
+  private String dbUnderReplication = null;

Review comment:
       This variable is used by commitTxn/AbortTxn to know that this is 
hiveReplTxn and requires some special handling. It would be again set to null 
only when commit/AbortTxn event comes for this opened transaction. 




-- 
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 578031)
    Time Spent: 3h 20m  (was: 3h 10m)

> Skip the repl events from getting logged in notification log
> ------------------------------------------------------------
>
>                 Key: HIVE-24909
>                 URL: https://issues.apache.org/jira/browse/HIVE-24909
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Haymant Mangla
>            Assignee: Haymant Mangla
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> Currently REPL dump events are logged and replicated as a part of replication 
> policy. Whenever one replication cycle completed, we always have one 
> transaction left open on the target corresponding to repl dump operation. 
> This will never be caught up without manually dealing with the transaction on 
> target cluster.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to