[
https://issues.apache.org/jira/browse/YUNIKORN-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539111#comment-17539111
]
Saad Ur Rahman edited comment on YUNIKORN-1213 at 5/18/22 10:11 PM:
--------------------------------------------------------------------
Thanks [~wwei], I think your suggestion of putting it under the _*scheduler*_
might be better. You are right about the _*partition*_ limitation the current
implementation will introduce. I will wait for a consensus on the issue from
[[email protected]|mailto:[email protected]] but switching the implementation to be under the
_*scheduler*_ should not be a hassle.
I will also update the documentation accordingly for the new settings.
was (Author: surahman):
Thanks [~wwei], I think your suggestion of putting it under the _*scheduler*_
might be better. You are right about the _*partition*_ limitation the current
implementation will introduce. I will wait for a consensus on the issue from
[[email protected]|mailto:[email protected]] but switching the implementation to be under the
_*scheduler*_ should not be a hassle.
> 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]
