[
https://issues.apache.org/jira/browse/YUNIKORN-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855123#comment-17855123
]
Dmitry commented on YUNIKORN-2646:
----------------------------------
With DEADLOCK_DISABLE_LOCK_ORDER it's spewing some other errors but nothing
about deadlocks. The scheduler got hung again today and was not scheduling. I
had to return back to default one again.
The log without DEADLOCK_DISABLE_LOCK_ORDER is attached.
[^yunikorn-logs.txt.gz]
> Deadlock detected during preemption
> -----------------------------------
>
> Key: YUNIKORN-2646
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2646
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Dmitry
> Assignee: Wilfred Spiegelenburg
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0, 1.5.2
>
> Attachments: yunikorn-logs-lock.txt.gz, yunikorn-logs.txt.gz
>
>
> Hitting deadlocks in 1.5.1
> The log is attached
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
