public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[bitnami/redis-cluster] Modify the readme file to describe the redis rdb persistence strategy (#55980) 

* Modify the readme file to describe the redis rdb persistence strategy

Signed-off-by: jianchen huang <huangjc7@foxmail.com>

* Modify the readme file to describe the redis rdb persistence strategy

Signed-off-by: jianchen huang <huangjc7@foxmail.com>

* Modify the readme file to describe the redis rdb persistence strategy

Signed-off-by: jianchen huang <huangjc7@foxmail.com>

---------

Signed-off-by: jianchen huang <huangjc7@foxmail.com>
This commit is contained in:
huangjc7 2024-02-03 01:12:20 +08:00 committed by GitHub
parent 5f877105c8
commit bf624b9854
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 43 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
bitnami/redis-cluster/README.md
View File

@ -217,6 +217,30 @@ Where you can add all the `node:port` that you want. The `--cluster-replicas` pa
Depending on the environment you're deploying into, you might run into issues where the cluster initialization is not completing successfully. One of the issue is related to the DNS lookup of the redis nodes performed during cluster initialization. By default, this DNS lookup is performed as soon as all the redis nodes reply to a successful ping.
However, in some environments such as Kubernetes, it can help to wait some time before performing this DNS lookup in order to prevent getting stale records. To this end, you can increase `REDIS_CLUSTER_SLEEP_BEFORE_DNS_LOOKUP` to a value around `30` which has been found to be good in most cases.
### Enable RDB persistence and set policies
When using RDB persistence and configuring related persistence strategies, it will be special. You need to use `#` to separate parameters.
1. Using `docker run`
```console
$ docker run --name redis-cluster \
-e REDIS_RDB_POLICY_DISABLED="900#1 300#10 60#10000" \
bitnami/redis-cluster:latest
```
2. Add parameters to the `docker-compose.yml` file present in this repository:
```yaml
redis-cluster:
...
environment:
...
- REDIS_RDB_POLICY_DISABLED="900#1 300#10 60#10000"
...
...
```
### Securing Redis(R) Cluster traffic
Starting with version 6, Redis(R) adds the support for SSL/TLS connections. Should you desire to enable this optional feature, you may use the aforementioned `REDIS_TLS_*` environment variables to configure the application.

19
bitnami/redis/README.md
View File

@ -331,6 +331,25 @@ services:
...
```
### Enable RDB persistence
When using RDB persistence and configuring related persistence strategies, it will be special. You need to use `#` to separate parameters.
```console
docker run --name redis -e REDIS_RDB_POLICY_DISABLED="900#1 300#10 60#10000" bitnami/redis:latest
```
Alternatively, add parameters to the `docker-compose.yml` file present in this repository:
```yaml
services:
redis:
...
environment:
- REDIS_RDB_POLICY_DISABLED="900#1 300#10 60#10000"
...
```
### Enabling Access Control List
Redis(R) offers [ACL](https://redis.io/topics/acl) since 6.0 which allows certain connections to be limited in terms of the commands that can be executed and the keys that can be accessed. We strongly recommend enabling ACL in production by specifiying the `REDIS_ACLFILE`.