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

Default Proc Limits equivalent with default k8s limits #45

Open
stevelitras opened this issue Oct 7, 2021 · 2 comments
Open

Default Proc Limits equivalent with default k8s limits #45

stevelitras opened this issue Oct 7, 2021 · 2 comments
Labels
blocked Issues waiting on other tickets to be resolved first enhancement New feature or request

Comments

@stevelitras
Copy link
Collaborator

The default of -2 for worker process can cause a problem on k8s (due to the pod seeing the CPUs allocated to the node, unrelated to the requests/limits setup. Have the default setup in LogStream equal the default request/limit values.
@bdalpe
Copy link
Contributor

bdalpe commented Sep 22, 2022

@stevelitras can you share your thoughts on how we could accomplish this?

@bdalpe bdalpe added the enhancement New feature or request label Sep 22, 2022
@bdalpe bdalpe added the blocked Issues waiting on other tickets to be resolved first label Mar 8, 2023
@eugene-cribl
Copy link

@stevelitras Is this now possible using CRIBL_MAX_WORKERS?
https://docs.cribl.io/stream/scaling/#allocate-a-maximum-number-of-worker-processes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Issues waiting on other tickets to be resolved first enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stevelitras @bdalpe @eugene-cribl