[ 
https://issues.apache.org/jira/browse/YUNIKORN-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539664#comment-17539664
 ] 

Craig Condit commented on YUNIKORN-1213:
----------------------------------------

Adding this from Slack so we don't lose it:
{quote}[Wilfred 
Spiegelenburg|https://app.slack.com/team/ULRU2BU6B]!https://slack-imgs.com/?c=1&o1=gu&url=https%3A%2F%2Fa.slack-edge.com%2Fproduction-standard-emoji-assets%2F13.0%2Fapple-small%2F1f468-1f3fb-200d-1f3eb%402x.png!
   [8:43 
AM|https://yunikornworkspace.slack.com/archives/CL9CRJ1KM/p1652967803284849]
Can we not mix the scheduler config with the queue configs?
The queue configs are reloaded and data is written into the config map when we 
update through the REST calls.
I would strongly recommend that we get a separate config for all this.
We have a large number of values that should move into a config object instead 
of just one or two.
{quote}So I guess we should go for it. As this is adding a new config section, 
it won’t be an incompatible change.{quote}
That depends on the parser and how the parser is configured. Having an unknown 
blob in the config may fail the parser.
We also return the config object via REST which would now include more data.
The rest response can be YAML or json. I think we need to be careful here and 
not assume it is backwards compatible.{quote}
We may want to pause on this one for a bit as there's some concern about 
updating the existing configmap vs. creating a new one.

> The interval of the background health checker needs to be configurable
> ----------------------------------------------------------------------
>
>                 Key: YUNIKORN-1213
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1213
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - scheduler
>            Reporter: Weiwei Yang
>            Priority: Major
>              Labels: pull-request-available
>
> YUNIKORN-1107 adds a background running health checker to verify the 
> scheduler data correctness in the fixed time interval 30s: 
> https://github.com/apache/yunikorn-core/blob/3ba91fb8a41c0fd0dd6243326e583dea5167199f/pkg/scheduler/health_checker.go#L34.
>  We need to make this configurable, either let the user set a longer/shorter 
> interval, or completely disable it.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to