[
https://issues.apache.org/jira/browse/YUNIKORN-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538573#comment-17538573
]
Weiwei Yang commented on YUNIKORN-1213:
---------------------------------------
hi [~surahman]
{quote}
For backward compatibility, we will likely have to retain the default check
interval of 30 sec if no entries are found in the ConfigMap.
{quote}
Correct, if nothing is set, the default value is enabled, and interval is 30s.
For retrieving the configs, we should be able to access all configs via
https://github.com/apache/yunikorn-core/blob/master/pkg/common/configs/configs.go.
So we can get the configs by something like
"configs.ConfigContext.Get(schedulerContext.GetPolicyGroup())" I guess.
When healthcheck is disabled, we shouldn't start the healthcheck thread. And
the healthcheck endpoint can return either an empty result or something like
you proposed. I think it should be fine.
> 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
>
> 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]
