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

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

                Author: ASF GitHub Bot
            Created on: 27/Feb/23 13:53
            Start Date: 27/Feb/23 13:53
    Worklog Time Spent: 10m 
      Work Description: deniskuzZ commented on code in PR #3576:
URL: https://github.com/apache/hive/pull/3576#discussion_r1118764958


##########
ql/src/test/org/apache/hadoop/hive/ql/txn/compactor/TestCleaner2.java:
##########
@@ -23,6 +23,6 @@
 public class TestCleaner2 extends TestCleaner {
   @Override
   boolean useHive130DeltaDirName() {
-    return false;
+    return true;

Review Comment:
   no, but we have TestCleaner & TestCleaner2 running the same stuff





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

    Worklog Id:     (was: 847828)
    Time Spent: 4h 10m  (was: 4h)

> Cleaner shouldn't be blocked by global min open txnId
> -----------------------------------------------------
>
>                 Key: HIVE-26704
>                 URL: https://issues.apache.org/jira/browse/HIVE-26704
>             Project: Hive
>          Issue Type: Task
>            Reporter: Denys Kuzmenko
>            Assignee: Denys Kuzmenko
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> *Single transaction blocks cluster-wide Cleaner operations*
> Currently, if there is a single long-running transaction that can prevent the 
> Cleaner to clean up any tables. This causes file buildup in tables, which can 
> cause performance penalties when listing the directories (note that the 
> compaction is not blocked by this, so unnecessary data is not read, but the 
> files remain there which causes performance penalty). 
> We can reduce the protected files from the open transaction if we have 
> query-table correlation data stored in the backend DB, but this change will 
> need the current method of recording that detail to be revisited. 
> The naive and somewhat backward-compatible approach is to capture the 
> minOpenWriteIds per table. It involves a non-mutation operation (as in, there 
> is no need for the HMS DB to wait for another user’s operation to record it). 
> This does spew data writes into the HMS backend DB, but this is a blind 
> insert operation that can be group-committed across many users. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to