[
https://issues.apache.org/jira/browse/HIVE-26145?focusedWorklogId=787264&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-787264
]
ASF GitHub Bot logged work on HIVE-26145:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Jul/22 00:22
Start Date: 02/Jul/22 00:22
Worklog Time Spent: 10m
Work Description: github-actions[bot] closed pull request #3215:
HIVE-26145: Disable notification cleaner if interval is zero
URL: https://github.com/apache/hive/pull/3215
Issue Time Tracking
-------------------
Worklog Id: (was: 787264)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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.10#820010)
