hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Somani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-21841) Leader election in HMS to run housekeeping tasks.
Date Fri, 14 Jun 2019 08:38:00 GMT

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

Abhishek Somani commented on HIVE-21841:
----------------------------------------

[~ashutosh.bapat] as I understand it currently, multiple HMS's co-ordinate amongst each other
and ensure that only one of them is doing the job at a time by locking an entry in the db,
in the AUX_TABLE. We think that its not good enough?

> Leader election in HMS to run housekeeping tasks.
> -------------------------------------------------
>
>                 Key: HIVE-21841
>                 URL: https://issues.apache.org/jira/browse/HIVE-21841
>             Project: Hive
>          Issue Type: New Feature
>    Affects Versions: 4.0.0
>            Reporter: Ashutosh Bapat
>            Assignee: Ashutosh Bapat
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>         Attachments: HIVE-21841.01.patch, HIVE-21841.02.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> HMS performs housekeeping tasks. When there are multiple HMSes we need to have a leader
HMS elected which will carry out those housekeeping tasks. 
> These tasks include execution of compaction tasks, auto-discovering partitions for external
tables, generation of compaction tasks, repl thread etc.
> Note that, though the code for compaction tasks, auto-discovery of partitions etc. is
in Hive, the actual tasks are initiated by an HMS configured to do so. So, leader election
is required only for HMS and not for HS2.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message