[ https://issues.apache.org/jira/browse/YUNIKORN-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768932#comment-17768932 ]
Sidharth Mereddy edited comment on YUNIKORN-1997 at 9/25/23 10:34 PM: ---------------------------------------------------------------------- added patch to fix the issues. Status page works well now. was (Author: JIRAUSER295932): added patch to fix the issues. Status page works well now. > 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: After patch.png, Before patch.png, 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-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org