[
https://issues.apache.org/jira/browse/HIVE-22351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesus Camacho Rodriguez updated HIVE-22351:
-------------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to master, thanks [~jfs]!
> Fix incorrect threaded ObjectStore usage in TestObjectStore
> -----------------------------------------------------------
>
> Key: HIVE-22351
> URL: https://issues.apache.org/jira/browse/HIVE-22351
> Project: Hive
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: John Sherman
> Assignee: John Sherman
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-22351.1.patch, HIVE-22351.2.patch
>
>
> TestObjectStore#testConcurrentDropPartitions shares the same ObjectStore
> object across two threads doing concurrent drops. ObjectStore isn't thread
> safe. I've seen occasional deadlocks where one thread is rolling back and
> another is trying to commit with each thread waiting on the other (one is
> holding an object lock via a synchronized method and another is holding the
> ExecutionContextThreadedImpl lock). I think the intent is to test
> dropPartition behavior and ensure the backing DB receives a rollback or abort
> on conflicting drops.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
