[HIVE-22351] Fix incorrect threaded ObjectStore usage in TestObjectStore

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.0
• Fix Version/s: 4.0.0-alpha-1
• Target Version/s: 4.0.0
• Assignee: John Sherman
• Reporter: John Sherman
• Created: 15/Oct/19 23:35
• Updated: 27/Feb/24 22:23
• Resolved: 18/Oct/19 18:16

Description

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.

Issue Links

• is caused by: HIVE-16839 Unbalanced calls to openTransaction/commitTransaction when alter the same partition concurrently