You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Sidharth Mereddy (Jira)" <ji...@apache.org> on 2023/09/25 22:29:00 UTC
[jira] [Updated] (YUNIKORN-1997) Yunikorn Status page fails when scheduler is not healthy
[ https://issues.apache.org/jira/browse/YUNIKORN-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sidharth Mereddy updated YUNIKORN-1997:
---------------------------------------
Attachment: patch.txt
> Yunikorn Status page fails when scheduler is not healthy
> --------------------------------------------------------
>
> Key: YUNIKORN-1997
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1997
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Sidharth Mereddy
> Priority: Major
> Attachments: patch.txt
>
>
> when atleast 1 component of scheduler health check status updates to succeeded:"false", status page stops working with error - "Oops, something went wrong. YuniKorn is not accessible."
> Rest Call shows on both 9889 and 9080 port -
> {"status_code":503,"message":"Scheduler is not healthy","description":"Scheduler is not healthy"}
> All other rest calls work fine on both ports.
> The 503 most likely causes the code in the web UI to shut down without a possibility to start again.
> I do not see any code that would handle/retry the 503. It also does not make sense for me to return that code in this case
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org