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

Setting "MemorySize" has no effect on maxmemory #414

Closed
MrBlaise opened this issue May 23, 2024 · 1 comment
Closed

Setting "MemorySize" has no effect on maxmemory #414

MrBlaise opened this issue May 23, 2024 · 1 comment

Comments

@MrBlaise
Copy link

MrBlaise commented May 23, 2024

Describe the bug

I am trying to limit the maximum memory garnet can use, however when I set it using the documented "MemorySize" I don't see it reflected when I query it using CONFIG GET maxmemory

Even though during startup I can see this line in the logs:

[000.2024-05-23 13:57:38.2895] (Information) <Options> [Store] Using log memory size of 2g

When I set it manually during runtime with CONFIG SET maxmemory 2g I immediately see it reflected as the memory usage of my instances will go down and keys will be reported evicted.

Steps to reproduce the bug

Deploy garnet like so: /garnet --config-import-path /etc/garnet/garnet.conf

garnet.conf:

{
    "MemorySize": "2g",
}

Expected behavior

The changes should be reflected in CONFIG GET maxmemory, and if the memory consumption is larger it should evict keys based on the policy instantly.

Screenshots

No response

Release version

v1.0.10 (linux x64)

IDE

No response

OS version

Debian

Additional context

No response

@MrBlaise
Copy link
Author

It turns out my test machines were improperly setup and this might not actually be an issue. I will close it and reopen if I can confirm for sure. Sorry for the noise.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant