Fix valkey memory settings #172
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request configures memory limits and eviction policies for Valkey nodes by setting a maximum memory usage and specifying the eviction policy in both configuration templates and cluster setup scripts.
Memory management improvements:
maxmemory 1gbinvalkey-primary.conf.j2,valkey-replica.conf.j2, andsentinel.conf.j2to restrict Valkey nodes to use a maximum of 1GB RAM. [1] [2] [3]maxmemory-policy allkeys-lruandmaxmemory 1gbto the configuration for both primary and replica nodes in the cluster setup filevalkey-cluster.yml, ensuring consistent eviction policy and memory limit across all nodes. [1] [2]