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.

Sign up for GitHub

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

Jump to bottom

Set up sysctls when tuning nodes #2457

Open
1 task
mflendrich opened this issue Feb 4, 2025 · 0 comments
Open
1 task

Set up sysctls when tuning nodes #2457

mflendrich opened this issue Feb 4, 2025 · 0 comments
Labels
kind/epic Categorizes issue as an epic. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@mflendrich
Copy link
Collaborator

mflendrich commented Feb 4, 2025 •
edited
Loading

Issue originally authored by tnozicka as #749

What should the feature do:
We should tune sysctls related to scylla on the scylla nodes. Ideally we need to keep a list in sync with what's in regular scylla deployment but enforcing that may not be realistic. Also some values may need to be raised as we could run multiple scylla pods per kubernetes node.

What is use case behind this feature:
Some sysctls can be set directly on our CR but only those that are namespaced (https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#setting-sysctls-for-a-pod).
fs.inotify.max_user_instances is one of the cases that aren't namespaced and scylla needs them scylladb/scylladb#7700

Additional Information:
https://scylladb-users.slack.com/archives/CCC9J41FW/p1628195109003700

Tasks
Preview Give feedback
  1. Remove the workaround DaemonSet setting fs.aio-max-nr on CI worker nodes #1385
    kind/cleanup priority/backlog triage/accepted
    rzetelskik
@mflendrich mflendrich added kind/epic Categorizes issue as an epic. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Feb 4, 2025
@mflendrich mflendrich mentioned this issue Feb 4, 2025
Closed
@mflendrich mflendrich added the lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. label Feb 4, 2025
@mflendrich mflendrich marked this as a duplicate of #2424 Feb 12, 2025
@mflendrich mflendrich marked this as a duplicate of #2425 Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/epic Categorizes issue as an epic. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mflendrich @zimnx