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

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

                Author: ASF GitHub Bot
            Created on: 15/Apr/22 20:00
            Start Date: 15/Apr/22 20:00
    Worklog Time Spent: 10m 
      Work Description: kovjanos opened a new pull request, #3215:
URL: https://github.com/apache/hive/pull/3215

   ### What changes were proposed in this pull request?
   Make it possible to disable the db-notification cleaner(s) in an instance by 
configuring interval to zero, in case if there are multiple instances running 
   
   ### Why are the changes needed?
   In a highly concurrent deployment there can be multiple HMS instances 
running where it would be needed to run cleaner only in one instance to avoid 
overhead and/or conflict on the notification tables.
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   ### How was this patch tested?
   ...test is pending




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

            Worklog Id:     (was: 757492)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>          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)

Reply via email to