[
https://issues.apache.org/jira/browse/HIVE-26145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527445#comment-17527445
]
Stamatis Zampetakis commented on HIVE-26145:
--------------------------------------------
Looking at the available configuration properties and their description:
* metastore.event.db.listener.clean.interval
* metastore.event.db.listener.clean.startup.wait.interval
it's not very intuitive which one should be used to disable the cleaner and how.
Setting the {{clean.interval}} to zero could mean that you want the cleaner to
run ASAP without sleeping at all instead of deactivating it completely. On the
other hand if you set the {{startup.wait.interval}} to 100*365 you are sure
that the cleaner will not run in the next 100 years which I think it is as good
as being disabled.
> 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: 20m
> 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.7#820007)
