[YUNIKORN-2544] [UMBRELLA] Fix Yunikorn potential locking issues

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.1, 1.6.0
• Component/s: core - scheduler
• Target Version: 1.5.1, 1.6.0
• Assignee: Peter Bacsko
• Reporter: Peter Bacsko
• Created: 06/Apr/24 21:04
• Updated: 06/Sep/24 15:27
• Resolved: 22/Apr/24 15:46

Description

Go tool go-deadlock identified several potential deadlocks in Yunikorn.

Some of these do not cause problems right now, but a lock-related change in the future can trigger a deadlock.

Issue Links

• is related to: YUNIKORN-2521 Scheduler deadlock

Sub-Tasks

• Fix locking in RMProxy: Resolved
• Eliminate multiple lock calls from Queue: Resolved
• Eliminate read lock call from Queue.addChildQueue(): Closed
• Queue: clean up logic when adding application: Resolved
• Potential deadlock during concurrent bottom-up/top-down queue traversal: Resolved
• Fix locking in PartitionContext: Resolved
• Recursive locking when sending remove queue event: Resolved
• [core] Enable deadlock detection during unit tests: Resolved
• [shim] Enable deadlock detection during unit tests: Resolved