You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Redis container doesn't persist the data when the container is removed and recreated. It would be useful to document how to do that in production (at least) to be able to restore Celery queues.
This came up in #2781 where it was considered to use Redis as a cache for the information which users were last active.
Technical details:
Redash Version: 5.0.0
Browser/OS: Firefox 63.0/macOS 10.14
How did you install Redash: Docker
The text was updated successfully, but these errors were encountered:
jezdez
changed the title
Update redis container in compose config to persist data
Document how to persist redis container data between creations
Sep 27, 2018
start with persistent storage
$ docker run --name some-redis -d redis redis-server --save 60 1 --loglevel warning
There are several different persistence strategies to choose from. This one will save a snapshot of the DB every 60 seconds if at least 1 write operation was performed (it will also lead to more logs, so the loglevel option may be desirable). If persistence is enabled, data is stored in the VOLUME /data, which can be used with --volumes-from some-volume-container or -v /docker/host/dir:/data (see docs.docker volumes).
Issue Summary
Currently the Redis container doesn't persist the data when the container is removed and recreated. It would be useful to document how to do that in production (at least) to be able to restore Celery queues.
This came up in #2781 where it was considered to use Redis as a cache for the information which users were last active.
Technical details:
The text was updated successfully, but these errors were encountered: