You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Manoj Govindassamy (Jira)" <ji...@apache.org> on 2021/12/13 05:45:00 UTC

[jira] [Updated] (HUDI-2962) Support JVM based local process lock provider implementation

     [ https://issues.apache.org/jira/browse/HUDI-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manoj Govindassamy updated HUDI-2962:
-------------------------------------
    Summary: Support JVM based local process lock provider implementation  (was: Enable metadata table along with JVM local lock provider)

> Support JVM based local process lock provider implementation
> ------------------------------------------------------------
>
>                 Key: HUDI-2962
>                 URL: https://issues.apache.org/jira/browse/HUDI-2962
>             Project: Apache Hudi
>          Issue Type: Task
>            Reporter: Manoj Govindassamy
>            Assignee: Manoj Govindassamy
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.11.0
>
>
> Metadata table is disabled by default in master due to https://issues.apache.org/jira/browse/HUDI-2961. 
>  
> For the single writer + async table services deployment model, to protect against races, we can have a fairly light weight JVM local lock provider. This mean all the writes and the table services have to be running from the single JVM, like in the case of DeltaStreamer.  This doesn't cover the multi JVM writes, async table services though and a full fix for the same will be covered by HUDI-2961. For now to have the metadata table re-enabled at master, a JVM local locl provider should be sufficient. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)