-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
about REDIS_RDB_POLICY #72323
Comments
Hi @allegrox, thank you for opening this issue. You are right, setting the "save" config is buggy right now. It can be set multiple times and the resulting applied configuration would be the concatenation of all of those. To fix the issue, we should probably make the containers/bitnami/redis/7.4/debian-12/rootfs/opt/bitnami/scripts/libredis.sh Lines 416 to 425 in 1a0f63f
containers/bitnami/redis/7.4/debian-12/rootfs/opt/bitnami/scripts/libredis.sh Lines 48 to 65 in 1a0f63f
Would you like to contribute with a fix for this bug? PRs are more than welcome!! |
In my understanding, $REDIS_RDB_POLICY should contain a full policy content. Then saving the policy content is a process of replacing the existing policy, so you can clear the current policy before starting. |
…restarted ref: Issues bitnami#72323
Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close. Your contribution is greatly appreciated! |
Name and Version
bitnami/redis
What architecture are you using?
amd64
What steps will reproduce the bug?
https://github.com/bitnami/containers/blob/main/bitnami/redis/README.md
The readme documentation describes setting Enable Redis(R) RDB persistence in docker-compose.yml: redis.
But after installing this method configuration the container fails to start with an error:
Changed to the following method to start normally
- “REDIS_RDB_POLICY=900#1 600#5 300#10 120#50 60#1000 30#10000”
But I found another problem, every time I restarted the container, the contents of the CONFIG GET SAVE fetch would be incremented with the contents of
REDIS_RDB_POLICY
, e.g.:How do I configure the
REDIS_RDB_POLICY
parameter correctly?The text was updated successfully, but these errors were encountered: