From 44460b3ee313edcae5a566f9a026f83405553c7f Mon Sep 17 00:00:00 2001 From: Shunsuke Ise Date: Thu, 27 Jun 2024 18:06:56 +0900 Subject: [PATCH] fix: minimum feasible nodes 50->100 That the current `minFeasibleNodesToFind` is 100 instead of 50 (in docs). See `kubernetes/pkg/scheduler/schedule_one.go`. --- .../concepts/scheduling-eviction/scheduler-perf-tuning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/scheduling-eviction/scheduler-perf-tuning.md b/content/en/docs/concepts/scheduling-eviction/scheduler-perf-tuning.md index fd499c550f..1f59ed2e7b 100644 --- a/content/en/docs/concepts/scheduling-eviction/scheduler-perf-tuning.md +++ b/content/en/docs/concepts/scheduling-eviction/scheduler-perf-tuning.md @@ -103,9 +103,9 @@ percentageOfNodesToScore: 50 `percentageOfNodesToScore` must be a value between 1 and 100 with the default value being calculated based on the cluster size. There is also a hardcoded -minimum value of 50 nodes. +minimum value of 100 nodes. -{{< note >}}In clusters with less than 50 feasible nodes, the scheduler still +{{< note >}}In clusters with less than 100 feasible nodes, the scheduler still checks all the nodes because there are not enough feasible nodes to stop the scheduler's search early.