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

["Stamatis Zampetakis (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-26145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523119#comment-17523119 ] 

Stamatis Zampetakis commented on HIVE-26145:
--------------------------------------------

Which lock is the one to blame here?

What happens if you set the {{metastore.event.db.listener.clean.startup.wait.interval}} to a very big value? Wouldn't this be somewhat equivalent to disabling the cleaner?

> 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
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)