[
https://issues.apache.org/jira/browse/HUDI-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Xu updated HUDI-4065:
-----------------------------
Priority: Blocker (was: Major)
> Implement a self-releasing FileLock for multiple writers scenario
> -----------------------------------------------------------------
>
> Key: HUDI-4065
> URL: https://issues.apache.org/jira/browse/HUDI-4065
> Project: Apache Hudi
> Issue Type: Improvement
> Components: multi-writer
> Reporter: Jian Feng
> Assignee: Jian Feng
> Priority: Blocker
> Fix For: 0.12.0
>
>
> when using HiveMetastoreBasedLockProvider or ZookeeperBasedLockProvider, if
> the writer with locker crash before releasing the locker, no writers can
> obtain the locker anymore, hence can not cleaning/expiring the lock after a
> failed write.
> Instead of those lockers depending on external components, FIleBaseLocker
> only relies on FileSystem's atomic file creation behavior. an instant will
> be written to the file, so it will clean the lock when failing writer
> rollback. also can set expire strategy on it.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
