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

Request for supporting hugepage resource #3297

Open
silentred opened this issue Jul 7, 2023 · 1 comment
Open

Request for supporting hugepage resource #3297

silentred opened this issue Jul 7, 2023 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@silentred
Copy link

silentred commented Jul 7, 2023

What would you like to be added:

Worker container is able to use HugePage resource from Host.
Creating docker container with the argument --device=/dev/hugepages:/dev/hugepages may help.

Why is this needed:

To test applications that need HugePage to run, for example SDPK and some Databases.

Problem:

This may cause K8S Node resource consistency problem, if there are multiple nodes, which are enabled to use HugePage, on one machine. Therefore, this feature should be only used for testing purpose.
This issue comes with another question, it seems Memory resource has the same issue. If multiple nodes are created on one machine, each one of them can see all the memory from Host, but they cannot use all the memory.

@silentred silentred added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 7, 2023
@BenTheElder
Copy link
Member

This may cause K8S Node resource consistency problem, if there are multiple nodes, which are enabled to use HugePage, on one machine. Therefore, this feature should be only used for testing purpose.

When we test Kubernetes we use multiple nodes. What's the use case for this?

This issue comes with another question, it seems Memory resource has the same issue. If multiple nodes are created on one machine, each one of them can see all the memory from Host, but they cannot use all the memory.

Yes, in general resource limits are not best tested with nested containers and should use a VM or similar platform instead. See: #1963

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants