Minimale Redis-versie

AI-generated summary

The discussion revolves around the minimum Redis version requirement for Discourse, which is set at v6.0 despite Sidekiq only requiring v4.0+. andyv1 questions the rationale, noting Google Cloud Redis only supports v5. Falco explains that v6.0 is the version tested and used in production, and while older versions may work, they aren’t supported. Falco elaborates that Discourse uses Redis for multiple purposes beyond Sidekiq, including live updates via the message_bus gem, Rails cache, rate limiting, and semaphores. andyv1 seeks more details on Redis usage, and pfaffman shares that they’re using Google Cloud Redis but plan to migrate to AWS, suggesting potential compatibility concerns with managed services.

Hi,

I note the minimum version of Redis is specified at 6.0, but Sidekq only requires Redis v4.0+. discourse/docs/INSTALL.md at main · discourse/discourse · GitHub

I wish to use Google Cloud Redis, but it only supports v5.

What is the reason for Discourse requiring Redis v6?

That is the version we test and use in production in our hosting.

You may do your own due diligence and evaluate if it works with a previous version, but we don’t promise it will keep working with anything older than the version we recommend.

We use Redis for a lot more than Sidekiq.

That all said, the Redis feature set is pretty stable so it will probably work just okay today. But then you are on the hook testing upgrades carefully.

That sounds fair. An upgrade could use a new feature at any time.

What else does Discourse use Redis for? Or where in the code should I look?

Quite a lot actually.

We use Redis backend in the GitHub - discourse/message_bus: A reliable and robust messaging bus for Ruby and Rack · GitHub gem for live page updates, for the Rails cache, for the distributed rate limit, for our semaphore system, etc.

I’m running a deployment on GCP kubernetes, for just a bit longer. If I weren’t planning to move it to aws (it’s what the client wanted for an unrelated reason) I would probably switch to running my own redis and not use the Google one.