xiarixiaoyao opened a new pull request #3186:
URL: https://github.com/apache/hudi/pull/3186


   …ise this hive lock will be locked forever
   
   ## *Tips*
   - *Thank you very much for contributing to Apache Hudi.*
   - *Please review https://hudi.apache.org/contributing.html before opening a 
pull request.*
   
   ## What is the purpose of the pull request
   
   
   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)**
   
   ## Brief change log
   
   *(for example:)*
     - *Modify AnnotationLocation checkstyle rule in checkstyle.xml*
   
   ## Verify this pull request
   
   new UT added。
   
   ## Committer checklist
   
    - [ ] Has a corresponding JIRA in PR title & commit
    
    - [ ] Commit message is descriptive of the change
    
    - [ ] CI is green
   
    - [ ] Necessary doc changes done or have another open PR
          
    - [ ] For large changes, please consider breaking it into sub-tasks under 
an umbrella JIRA.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to