Skip to content
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

Document how to persist redis container data between creations #2860

Closed
jezdez opened this issue Sep 27, 2018 · 1 comment
Closed

Document how to persist redis container data between creations #2860

jezdez opened this issue Sep 27, 2018 · 1 comment

Comments

@jezdez
Copy link
Member

jezdez commented Sep 27, 2018

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:

  • Redash Version: 5.0.0
  • Browser/OS: Firefox 63.0/macOS 10.14
  • How did you install Redash: Docker
@guidopetri
Copy link
Contributor

I think we defer here to the Redis docker image docs:

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).

For more about Redis Persistence, see http://redis.io/topics/persistence.

Closing since this seems out of scope for redash, but feel free to reopen if you think otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants