[
https://issues.apache.org/jira/browse/YUNIKORN-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856602#comment-17856602
]
Peter Bacsko commented on YUNIKORN-2646:
----------------------------------------
[~dimm] if the problem re-appears, please create a new ticket and attach the
output of {{curl http://yunikorn-host:9080/ws/v1/stack}} or {{curl
http://yunikorn-host:9080/debug/pprof/goroutine?debug=2}} to see which
goroutine got stuck.
If that doesn't help, I'll compile a special version which ignores the stack
trace of the preemption code so the logs will not be flooded.
The attached log is of little use, it's full of false positive output.
> 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]
