Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: disable SchedulerQueueingHints feature flag by default #122289

Merged
merged 1 commit into from
Dec 13, 2023

Conversation

sanposhiho
Copy link
Member

@sanposhiho sanposhiho commented Dec 13, 2023

What type of PR is this?

/kind bug
/priority critical-urgent
/triage accepted

What this PR does / why we need it:

disable the feature gate of SchedulerQueueingHints by default.


We discussed at slack:
https://kubernetes.slack.com/archives/C2C40FMNF/p1702438650646789

And decided we'll make the feature gate for QHint disable by default. (Actually, there was a discussion of disablement for this before because we observed a memory consumption issue: #120622)
#122284 reinforces that idea. We'll make it enable by default once all issues here + memory consumption issue are addressed.

Which issue(s) this PR fixes:

Temporal fix for #122284

Special notes for your reviewer:

/cc @kubernetes/sig-scheduling-approvers
/cc @kerthcet
/cc @liggitt

Does this PR introduce a user-facing change?

The SchedulerQueueingHints feature gate moved back to disabled by default, due to unexpected memory use increases and to mitigate regressions found in some plugins' QueueingHint.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/bug Categorizes issue or PR as related to a bug. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Dec 13, 2023
@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Dec 13, 2023
@k8s-ci-robot
Copy link
Contributor

Please note that we're already in Test Freeze for the release-1.29 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.29.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Tue Dec 12 22:21:49 UTC 2023.

@k8s-ci-robot
Copy link
Contributor

@sanposhiho: GitHub didn't allow me to request PR reviews from the following users: kubernetes/sig-scheduling-approvers.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

What type of PR is this?

/kind bug
/priority critical-urgent
/triage accepted

What this PR does / why we need it:

disable the feature gate of SchedulerQueueingHints by default.

Which issue(s) this PR fixes:

Temporal fix for #122284

Special notes for your reviewer:

/cc @kubernetes/sig-scheduling-approvers
/cc @kerthcet
/cc @liggitt

Does this PR introduce a user-facing change?

SchedulerQueueingHints feature flag is disabled by default because we found a critical bug in some plugins' QueueingHint.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 13, 2023
@liggitt
Copy link
Member

liggitt commented Dec 13, 2023

/sig scheduling
/kind regression
/assign @alculquicondor
/lgtm

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. kind/regression Categorizes issue or PR as related to a regression from a prior release. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 13, 2023
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 13, 2023
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 2d338f8273d497d4ef6526c89610f1b6208a1bfa

@liggitt
Copy link
Member

liggitt commented Dec 13, 2023

/milestone v1.29
/approve
/hold for release team coordination

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 13, 2023
@k8s-ci-robot k8s-ci-robot added this to the v1.29 milestone Dec 13, 2023
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 13, 2023
@liggitt
Copy link
Member

liggitt commented Dec 13, 2023

/hold

There are unit tests that assume the gate is enabled. The minimal change is to enable the gate specifically for those tests:

func TestPriorityQueue_MoveAllToActiveOrBackoffQueue(t *testing.T) {
	c := testingclock.NewFakeClock(time.Now())
	logger, ctx := ktesting.NewTestContext(t)
	ctx, cancel := context.WithCancel(ctx)
	defer cancel()
	m := makeEmptyQueueingHintMapPerProfile()
+	defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.SchedulerQueueingHints, true)()
func TestRequeueByPermitRejection(t *testing.T) {
+	defer featuregatetesting.SetFeatureGateDuringTest(t, utilfeature.DefaultFeatureGate, features.SchedulerQueueingHints, true)()

@Priyankasaggu11929
Copy link
Member

LGTM from 1.29 Release Team, per the discussion in https://kubernetes.slack.com/archives/C2C40FMNF/p1702438650646789

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 13, 2023
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, sanposhiho

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Dec 13, 2023
@liggitt
Copy link
Member

liggitt commented Dec 13, 2023

/lgtm
/hold cancel

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Dec 13, 2023
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: f47771b4b06efe66b6bfae8b0265e0606ae77d72

@sanposhiho
Copy link
Member Author

@liggitt Thanks. Test_buildQueueingHintMap checks the feature gate actually, and I confirmed it passes without a change.

Running tool: /home/gitpod/go/bin/go test -timeout 30s -run ^Test_buildQueueingHintMap$ k8s.io/kubernetes/pkg/scheduler

ok  	k8s.io/kubernetes/pkg/scheduler	0.310s

Added SetFeatureGateDuringTest for the other two.

@ahg-g
Copy link
Member

ahg-g commented Dec 13, 2023

/lgtm

@sanposhiho
Copy link
Member Author

sanposhiho commented Dec 13, 2023

Talked with @liggitt, we'll cherry-pick this for v1.28.

@kerthcet
Copy link
Member

/lgtm

LGTM for quick fix, but seems we need to do more work later like in TestPriorityQueue_MoveAllToActiveOrBackoffQueue, as feature gate is always enabled.

@pacoxu
Copy link
Member

pacoxu commented Dec 13, 2023

we need to do more work later like in TestPriorityQueue_MoveAllToActiveOrBackoffQueue, as feature gate is always enabled.

Better to open an issue to track that.

@k8s-ci-robot k8s-ci-robot merged commit f2e85bc into kubernetes:master Dec 13, 2023
15 of 16 checks passed
@dims
Copy link
Member

dims commented Dec 13, 2023

thanks @sanposhiho

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. kind/regression Categorizes issue or PR as related to a regression from a prior release. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants