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

[ARCHIVED] Set up sysctls when tuning nodes #749

Closed
2 of 3 tasks
tnozicka opened this issue Aug 6, 2021 · 4 comments
Closed
2 of 3 tasks

[ARCHIVED] Set up sysctls when tuning nodes #749

tnozicka opened this issue Aug 6, 2021 · 4 comments
Assignees
@zimnx
Labels
lifecycle/migrated-away Indicates that this issue is archived and tracking continues in a copy. priority/archived Lowest priority possible - means that the issue is archived.

Comments

@tnozicka
Copy link
Contributor

tnozicka commented Aug 6, 2021 •
edited by rzetelskik
Loading

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. [ARCHIVED] Create enhancment proposal for automatic sysctl tuning #1372
    lifecycle/migrated-away priority/archived
    zimnx
  2. [ARCHIVED] Implement automatic sysctl tuning #1373
    lifecycle/migrated-away priority/archived
    zimnx
  3. Remove the workaround DaemonSet setting fs.aio-max-nr on CI worker nodes #1385
    kind/cleanup priority/backlog triage/accepted
    rzetelskik
@tnozicka tnozicka added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Aug 6, 2021
@tnozicka tnozicka added this to the v1.6 milestone Aug 6, 2021
@tnozicka tnozicka modified the milestones: v1.6, v1.7 Nov 26, 2021
@tnozicka tnozicka mentioned this issue Nov 14, 2022
Closed
@tnozicka tnozicka removed this from the v1.7 milestone Nov 14, 2022
@mykaul
Copy link
Contributor

mykaul commented Feb 5, 2023

Feasible for 1.9?

@tnozicka tnozicka added kind/epic Categorizes issue as an epic. and removed kind/feature Categorizes issue or PR as related to a new feature. labels Sep 5, 2023
@tnozicka tnozicka mentioned this issue Sep 6, 2023
Merged
@rzetelskik rzetelskik mentioned this issue Sep 6, 2023
Open
@tnozicka tnozicka mentioned this issue Nov 14, 2023
Merged
@scylla-operator-bot scylla-operator-bot
Copy link
Contributor

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 28, 2024
@tnozicka
Copy link
Contributor Author

tnozicka commented Jul 1, 2024

/remove-lifecycle stale
/triage accepted

@scylla-operator-bot scylla-operator-bot bot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 1, 2024
@tnozicka tnozicka mentioned this issue Jul 9, 2024
Merged
@tnozicka tnozicka closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2025
@mflendrich mflendrich added lifecycle/migrated-away Indicates that this issue is archived and tracking continues in a copy. priority/archived Lowest priority possible - means that the issue is archived. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/epic Categorizes issue as an epic. labels Feb 4, 2025
@mflendrich mflendrich changed the title Set up sysctls when tuning nodes [ARCHIVED] Set up sysctls when tuning nodes Feb 4, 2025
@mflendrich
Copy link
Collaborator

Will be tracked in #2457.

@mflendrich mflendrich mentioned this issue Feb 4, 2025
Open
@scylladb scylladb locked and limited conversation to collaborators Feb 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@zimnx zimnx

Labels
lifecycle/migrated-away Indicates that this issue is archived and tracking continues in a copy. priority/archived Lowest priority possible - means that the issue is archived.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mflendrich @zimnx @mykaul @tnozicka