artin/self_hosted_sentry
1
0
Fork 0
mirror of https://github.com/getsentry/self-hosted.git synced 2026-02-06 10:57:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(redis): Use a safer eviction rule (#3432)

Browse Source 
Follow up to https://github.com/getsentry/self-hosted/pull/3427#issuecomment-2485612688
This commit is contained in:
Burak Yigit Kaya 2024-11-19 16:34:41 +00:00 committed by GitHub
parent c3814f0807
commit 0b0d0c8e54
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
redis.conf
View File

@ -14,13 +14,14 @@
maxmemory 0
# maxmemory-policy allkeys-lru
#
# This setting determines how Redis evicts keys when it reaches the memory limit.
# 'allkeys-lru' evicts the least recently used keys from all keys stored in Redis,
# `allkeys-lru` evicts the least recently used keys from all keys stored in Redis,
# allowing frequently accessed data to remain in memory while older data is removed.
#
# Example:
# maxmemory-policy allkeys-lru # Use LRU eviction for all keys
# That said we use `volatile-lru` as Redis is used both as a cache and processing
# queue in self-hosted Sentry.
# > The volatile-lru and volatile-random policies are mainly useful when you want to
# > use a single Redis instance for both caching and for a set of persistent keys.
# > However, you should consider running two separate Redis instances in a case like
# > this, if possible.
maxmemory-policy allkeys-lru
maxmemory-policy volatile-lru