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

Operator OOM due to too low resource limits in example #357

Closed
zimnx opened this issue Feb 2, 2021 · 0 comments · Fixed by #360
Closed

Operator OOM due to too low resource limits in example #357

zimnx opened this issue Feb 2, 2021 · 0 comments · Fixed by #360
Assignees
@zimnx
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@zimnx
Copy link
Collaborator

zimnx commented Feb 2, 2021

Describe the bug

Operator might OOM due to too harsh memory limit in Operator example.
We should reevaluate the limits.

Environment:

  • Platform: GKE
  • Scylla-operator version: e.g.: master
@zimnx zimnx added the kind/bug Categorizes issue or PR as related to a bug. label Feb 2, 2021
@zimnx zimnx changed the title Operator OOM due to too allocated low resources in example Operator OOM due to too low resource limits in example Feb 2, 2021
@zimnx zimnx self-assigned this Feb 3, 2021
zimnx added a commit that referenced this issue Feb 3, 2021
@zimnx
config: limit operator memory to 100Mi (#357)
cfb5048 
Measurements show Operator can use 50MB of RSS memory
when multpile racks are added to Scylla cluster.
So double limit seems reasonable.

Fixes #357
@zimnx zimnx mentioned this issue Feb 3, 2021
Merged
zimnx added a commit that referenced this issue Feb 3, 2021
@zimnx
config: remove operator memory limit (#357)
9c46de0 
Measurements show Operator can use 50MB of RSS memory
when multpile racks are added to Scylla cluster.
Although it scales with number of objects, so no limit
is better. User may define his own limits if needed.

Fixes #357
@zimnx zimnx closed this as completed in #360 Feb 3, 2021
zimnx added a commit that referenced this issue Feb 3, 2021
@zimnx
config: remove operator memory limit (#357)
4520f59 
Measurements show Operator can use 50MB of RSS memory
when multpile racks are added to Scylla cluster.
Although it scales with number of objects, so no limit
is better. User may define his own limits if needed.

Fixes #357
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zimnx zimnx

Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

config: remove operator memory limit (#357) scylladb/scylla-operator
1 participant
@zimnx