[
https://issues.apache.org/jira/browse/YUNIKORN-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-481.
--------------------------------------------
Fix Version/s: 0.10
Resolution: Fixed
Change has been merged, waiting on YUNIKORN-480 to also merge to be able to
progress that one
> deadlock when removing allocation ask
> -------------------------------------
>
> Key: YUNIKORN-481
> URL: https://issues.apache.org/jira/browse/YUNIKORN-481
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Affects Versions: 0.10
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.10
>
>
> A new deadlock was introduced in the scheduler as part of the refactor.
> The deadlock can occur when an allocationAsk is removed from an application
> while the application is scheduled at the same point in time.
> The removeAllocationAsk() call in the partitionContext is a write locked call
> taking the context lock it later tries to take the application write lock.
> While scheduling to check the nodes we are retrieving the node iterator from
> the partition. This retrieval is done by a write locked application which
> needs a read lock on the partition.
> The removal of the ask should not hold the write lock on the partition while
> updating the application.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
