[
https://issues.apache.org/jira/browse/YUNIKORN-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541195#comment-17541195
]
Craig Condit commented on YUNIKORN-1213:
----------------------------------------
I agree we need a design doc and an umbrella JIRA to cover config changes.
[~wilfreds] raises some very valid concerns, and I think we need to be sure
they are addressed. Personally, I think using a single config is not really
feasible; that's going to have lots of challenges such as how to handle
updates, whether configs can be auto-refreshed, who has permission to do those
refreshes, etc. At the very least, a second configmap for service configs (as
opposed to queue configs) I think makes sense. We may also want one for the
admission controller, as this would allow us to deprecate most of our env-var
and cmd-line based configs.
> 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
> Assignee: Saad Ur Rahman
> 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]
