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

Change experimental-memory-mlock flag to memory-mlock #19273

Closed
wants to merge 7 commits into from

Conversation

jmao-dd
Copy link
Contributor

@jmao-dd jmao-dd commented Jan 25, 2025

@k8s-ci-robot
Copy link

Hi @jmao-dd. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

@jmao-dd
Copy link
Contributor Author

jmao-dd commented Jan 25, 2025

After reading through the comments on #19124 I realized we don't want to migrate this flag to feature gate any more. I will change the PR to accept both --experimental-memory-mlock and --memory-mlock.

@jmao-dd jmao-dd marked this pull request as draft January 25, 2025 17:59
@jmao-dd jmao-dd changed the title migrate experimental-memory-mlock to feature gate Change experimental-memory-mlock flag to memory-mlock Jan 25, 2025
Copy link

codecov bot commented Jan 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.80%. Comparing base (532c601) to head (73c37b3).

Additional details and impacted files
Files with missing lines Coverage Δ
server/config/config.go 80.23% <ø> (ø)
server/embed/config.go 79.65% <100.00%> (+0.06%) ⬆️
server/embed/etcd.go 76.49% <100.00%> (ø)
server/etcdmain/config.go 73.17% <100.00%> (+0.33%) ⬆️
server/storage/backend.go 72.72% <100.00%> (ø)

... and 26 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #19273      +/-   ##
==========================================
- Coverage   68.87%   68.80%   -0.07%     
==========================================
  Files         420      420              
  Lines       35680    35684       +4     
==========================================
- Hits        24573    24554      -19     
- Misses       9685     9704      +19     
- Partials     1422     1426       +4     

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 532c601...73c37b3. Read the comment docs.

Since the memory mlock feature has been added as an experimental feature since v3.5 we want
to promote it as a stable feature as memory-mlock in v3.6. In v3.7 we will retire the
experimental-memory-mlock flag.

Signed-off-by: Jiayin Mao <[email protected]>
@jmao-dd jmao-dd marked this pull request as ready for review January 25, 2025 22:21
@ahrtr
Copy link
Member

ahrtr commented Jan 26, 2025

I don't think this PR is correct, please follow the same pattern as #19267

@jmao-dd
Copy link
Contributor Author

jmao-dd commented Jan 26, 2025

I don't think this PR is correct, please follow the same pattern as #19267

Got it. Will update.

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jmao-dd
Once this PR has been reviewed and has the lgtm label, please assign spzala for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

Signed-off-by: Jiayin Mao <[email protected]>
@jmao-dd
Copy link
Contributor Author

jmao-dd commented Jan 26, 2025

The history of this PR is too complex to squash into one commit so I created a new PR #19277

@jmao-dd jmao-dd closed this Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants