You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Janos Kovacs (Jira)" <ji...@apache.org> on 2022/04/15 19:07:00 UTC

[jira] [Assigned] (HIVE-26145) Disable notification cleaner if interval is zero

     [ https://issues.apache.org/jira/browse/HIVE-26145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Janos Kovacs reassigned HIVE-26145:
-----------------------------------


> Disable notification cleaner if interval is zero
> ------------------------------------------------
>
>                 Key: HIVE-26145
>                 URL: https://issues.apache.org/jira/browse/HIVE-26145
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Metastore
>            Reporter: Janos Kovacs
>            Assignee: Janos Kovacs
>            Priority: Major
>
> Many of the housekeeping/background tasks can be turned off in case of having multiple instances running parallel. 
> Some are controlled via the housekeeping node configuration, others are not started if their frequency is set to zero.
> The DB-Notification cleaner unfortunately doesn't have this functionality which makes all instances to race for the lock on the backend HMS database. 
> Goal is to add change to be able to turn cleaner off in case if there are multiple instances running (be able to bound it to the housekeeping instance).  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)