[
https://issues.apache.org/jira/browse/YUNIKORN-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541190#comment-17541190
]
Weiwei Yang commented on YUNIKORN-1213:
---------------------------------------
Thanks [~wilfreds], [~surahman]. Based on what has been discussed, and concerns
raised, I can see two options
1) Use 1 configmap for the scheduler configs, adding a section for global
scheduler configs. This section is *immutable*. That means if the user wants to
change anything in this section, they need to restart the scheduler. Then the
hot-refresh is still working as before, just parse and update the partitions
section.
2) Add another configmap for scheduler configs, and the configmap is
*immutable*. (see:
https://kubernetes.io/docs/concepts/configuration/configmap/#configmap-immutable).
Our configwatcher won't look at this configmap. The changes will be mainly on
the deployment side as we need to attach another configmap to the scheduler pod.
any other solutions?
> 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]
