Replies: 4 comments
-
Hi @roehnan, thanks for filing this issue!
If I may, can I ask a few questions? |
Beta Was this translation helpful? Give feedback.
-
Hello @chakaz - This is a 72-core node from our Kubernetes cluster. I'll try the Do you have any recommendation on the settings? Since I am planning on requesting 8 cores for the deployment, I am wondering if 16 threads (2 per core) is reasonable? |
Beta Was this translation helpful? Give feedback.
-
My recommendation would be:
|
Beta Was this translation helpful? Give feedback.
-
Sounds good and thank you for the quick feedback! |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
When running on Kubernetes, the maxmemory that Dragonfly DB decides that it needs for itself is not sufficient for the amount of CPU resources requested and it refuses to start unless
--maxmemory
is specified manually.Dragonfly DB knows that more memory is available and it also knows how much memory is required to support the CPU requests, but chooses a smaller amount and fails to load.
Here is the log of the failure to run:
To Reproduce
Steps to reproduce the behavior:
--maxmemory
inextraArgs
.Expected behavior
maxmemory
(when not supplied as a command-line arg) should be determined based on available resources and CPU/thread requirements.Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Reproducible Code Snippet
Dragonfly DB installed via helm:
Contents of
myvals.yaml
:Beta Was this translation helpful? Give feedback.
All reactions