[jira] [Work logged] (HIVE-26704) Cleaner shouldn't be blocked by global min open txnId

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 04/Jan/23 00:19
            Start Date: 04/Jan/23 00:19
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #3576:
URL: https://github.com/apache/hive/pull/3576#issuecomment-1370355426

   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 dev@hive.apache.org list if the patch is in need of reviews.




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

    Worklog Id:     (was: 836765)
    Time Spent: 0.5h  (was: 20m)

> 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: 0.5h
>  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)