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

Reduce guarantee memory to avoid going beyond the allocatable value #804

Merged
merged 1 commit into from
Nov 5, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion config/hubs/meom-ige.cluster.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ hubs:
description: "~32 CPU, ~128G RAM"
damianavila marked this conversation as resolved.
Show resolved Hide resolved
kubespawner_override:
mem_limit: 128G
mem_guarantee: 110G
mem_guarantee: 100G
node_selector:
node.kubernetes.io/instance-type: n1-standard-32
- display_name: "Huge"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there something similar we should do for "huge"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fetching info from the nodes:

small >> 5758056Ki >> 5.75 GB allocatable (mem_guarantee: 5GB)
medium  >> 27155328Ki >> 27.15 GB allocatable (mem_guarantee: 25GB)
large >> 56183024Ki >> 56.18 GB allocatable (mem_guarantee: 50GB)
very large >> 114336712Ki >> 114.33G allocatable (mem_guarantee: 100GB with this PR)
huge >> 235367296Ki >> 235.37GB allocatable (mem_guarantee: 220G)

I think we are OK with the huge one but happy to discuss all the other values 😉 .

Expand Down