[jira] [Updated] (HUDI-2099) hive lock which state is WATING should be released, otherwise this hive lock will be locked forever

2021-07-30 Thread Udit Mehrotra (Jira)


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

Udit Mehrotra updated HUDI-2099:

Status: In Progress  (was: Open)

>  hive lock which state is WATING should be released,  otherwise this hive 
> lock will be locked forever
> -
>
> Key: HUDI-2099
> URL: https://issues.apache.org/jira/browse/HUDI-2099
> Project: Apache Hudi
>  Issue Type: Bug
>  Components: Common Core
>Affects Versions: 0.8.0
> Environment: spark3.1.1
> hive3.1.1
> hadoop3.1.1
>Reporter: tao meng
>Assignee: tao meng
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.8.0
>
>
> when we acquire hive lock failed and the lock state is WATING, we should 
> release this WATING lock; otherwise this hive lock will be locked forever。
> test step:
> use hive lock to control concurrent write for hudi, let‘s call this lock 
> hive_lock
> start three writers to write hudi table by using hive_lock concurrently, one 
> of the writer will failed to acquire hive lock due to competition issues。
> *Exception in thread "main" org.apache.hudi.exception.HoodieLockException: 
> Unable to acquire lock, lock object LockResponse(lockid:76, state:WAITING)*
>  
> start another writer to write hudi table by using same hive_lock, then we 
> find hive_lock is locked forever, we have no way to acquire it
> *Exception in thread "main" org.apache.hudi.exception.HoodieLockException: 
> Unable to acquire lock, lock object LockResponse(lockid:87, state:WAITING)*



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (HUDI-2099) hive lock which state is WATING should be released, otherwise this hive lock will be locked forever

2021-06-29 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated HUDI-2099:
-
Labels: pull-request-available  (was: )

>  hive lock which state is WATING should be released,  otherwise this hive 
> lock will be locked forever
> -
>
> Key: HUDI-2099
> URL: https://issues.apache.org/jira/browse/HUDI-2099
> Project: Apache Hudi
>  Issue Type: Bug
>  Components: Common Core
>Affects Versions: 0.8.0
> Environment: spark3.1.1
> hive3.1.1
> hadoop3.1.1
>Reporter: tao meng
>Assignee: tao meng
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.8.0
>
>
> when we acquire hive lock failed and the lock state is WATING, we should 
> release this WATING lock; otherwise this hive lock will be locked forever。
> test step:
> use hive lock to control concurrent write for hudi, let‘s call this lock 
> hive_lock
> start three writers to write hudi table by using hive_lock concurrently, one 
> of the writer will failed to acquire hive lock due to competition issues。
> *Exception in thread "main" org.apache.hudi.exception.HoodieLockException: 
> Unable to acquire lock, lock object LockResponse(lockid:76, state:WAITING)*
>  
> start another writer to write hudi table by using same hive_lock, then we 
> find hive_lock is locked forever, we have no way to acquire it
> *Exception in thread "main" org.apache.hudi.exception.HoodieLockException: 
> Unable to acquire lock, lock object LockResponse(lockid:87, state:WAITING)*



--
This message was sent by Atlassian Jira
(v8.3.4#803005)