Skip to content

Commit 2f63018

Browse files
author
Jonathan Visser
committed
Format files according to mdformat
1 parent 3f21c3c commit 2f63018

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/hypernode-platform/redis/how-to-change-redis-eviction-policy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
myst:
33
html_meta:
4-
description: Changing the Redis eviction policy on Hypernode with hypernode-systemctl. Learn which policies are available and how to verify the active Redis maxmemory-policy.
4+
description: Changing the Redis eviction policy on Hypernode with hypernode-systemctl.
5+
Learn which policies are available and how to verify the active Redis maxmemory-policy.
56
title: Changing the Redis eviction policy on Hypernode
67
---
78

89
# Changing the Redis eviction policy
910

1011
You can change the Redis `maxmemory-policy` with `hypernode-systemctl settings redis_eviction_policy`. This policy determines which keys Redis can evict when memory is full.
1112

12-
1313
## Available policies
1414

1515
The following values are supported for `redis_eviction_policy`:
@@ -98,4 +98,4 @@ random.
9898
- Setting a TTL on cache keys is still recommended, even when using an `allkeys-` policy.
9999
- Policies starting with `volatile-` only apply to keys with a TTL.
100100
- If not enough keys have a TTL, Redis may not be able to evict enough data with a `volatile-` policy, and write operations may fail.
101-
- Changing the policy does not remove existing keys immediately.
101+
- Changing the policy does not remove existing keys immediately.

0 commit comments

Comments
 (0)