[
https://issues.apache.org/jira/browse/YUNIKORN-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated YUNIKORN-950:
----------------------------------
Description:
In YUNIKORN-940, only the following route was introduced:
{noformat}
route{
"Scheduler",
"PUT",
"/ws/v1/periodicstatedump/{switch}/{periodSeconds}",
handlePeriodicStateDump,
},
{noformat}
This is not enough. If we want to gracefully handle the situation when either
"switch" or both "switch" and "periodSeconds" are missing, then we have to
define them explicitly.
was:
In YUNIKORN-940, only the following route was specified:
{noformat}
route{
"Scheduler",
"PUT",
"/ws/v1/periodicstatedump/{switch}/{periodSeconds}",
handlePeriodicStateDump,
},
{noformat}
This is not enough. If we want to gracefully handle the situation when either
"switch" or both "switch" and "periodSeconds" are missing, then we have to
define them explicitly.
> Add missing HTTP routes regarding statedump feature
> ---------------------------------------------------
>
> Key: YUNIKORN-950
> URL: https://issues.apache.org/jira/browse/YUNIKORN-950
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
>
> In YUNIKORN-940, only the following route was introduced:
> {noformat}
> route{
> "Scheduler",
> "PUT",
> "/ws/v1/periodicstatedump/{switch}/{periodSeconds}",
> handlePeriodicStateDump,
> },
> {noformat}
> This is not enough. If we want to gracefully handle the situation when either
> "switch" or both "switch" and "periodSeconds" are missing, then we have to
> define them explicitly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
