You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2022/05/18 21:26:00 UTC
[jira] [Resolved] (YUNIKORN-1218) Scheduler crashed with concurrent map access error in health checker
[ https://issues.apache.org/jira/browse/YUNIKORN-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Condit resolved YUNIKORN-1218.
------------------------------------
Fix Version/s: 1.1.0
Target Version: 1.1.0
Resolution: Fixed
Merged to master. Thanks [~wwei].
> Scheduler crashed with concurrent map access error in health checker
> --------------------------------------------------------------------
>
> Key: YUNIKORN-1218
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1218
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.1.0
>
> Attachments: reproduce.patch, stacktrace.log
>
>
> After YUNIKORN-1107, the health checker runs as a background thread in 30s interval. We observed a few scheduler restarts in the past week that seems to be caused by this thread, because it has an unsafe access to the partition context without proper read lock. I have uploaded a patch to reproduce this locally, and a file of the stack trace when crash happens.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org