I keep getting timeouts from redis/hiredis and would like to increase the timeout to see if it fixes the issue. (I am connecting to a remote redis instance, not on the same instance as Discourse.) Additionally I need to turn off CLIENT operations as well. Afaict both of these would be done in a red…

You can config redis using the app.yml section Beginning of custom commands with something like - replace: filename: "/etc/redis/redis.conf" from: "daemonize yes" to: ""

I’m sure I am misunderstanding something here, but when I see /etc/… I assume that is happening on the vm running the redis server. Am I wrong in that reading? I am trying to change how the Discourse rails app communicates with the remote redis instance so that it (the client side) will make those …

Oh I see now. You want to pass a new parameters here: app/models/global_setting.rb main replica_host replica_port ].each do |s| if val = self.public_send("db_#{s}") hash[s] = val end end …

Would setting no CLIENT ops here too be viable? (eg “id = nil”)

I’m not familiar with restricting the CLIENT ops, can you share more about your use case and why is this necessary?

Some Redis setups (specifically cloud providers) do not allow the CLIENT operation. You can prevent this from occurring by setting “id = nil” in the redis configuration. This is an issue I have run into with sidekiq. Other apps that use sidekiq have noted this as an issue: https://github.com/mperh…

[imagen] Shane_Liebling: Some Redis setups (specifically cloud providers) do not allow the CLIENT operation. I don’t think we ever hit this in AWS Elasticache offering, and also didn’t hear anything from colleagues working with Azure. What is the cloud provider that is failing for you?

Running against Google Cloud’s Memorystore.

Oh that is interesting to know. A PR to allow setting custom REDIS_CLIENT_ID and REDIS_TIMEOUT, with current values as defaults sounds a good idea.

So if you look at https://github.com/discourse/discourse/compare/master...shanel:master you’ll see the necessary edit for the client id. (Turns out that is the only one I needed.) Unfortunately I am currently not allowed by my job to sign your release form. I could try to get my SVP to okay it, but…

Is there a way to change the redis connection timeout?

Soporte Instalación

Falco (Falco) Separó este tema 13 Febrero, 2021 05:45 16

A post was split to a new topic: Using Digital Ocean managed Redis with Discourse

Tema		Respuestas	Vistas
Redis connection timed out Self-hosting	30	9623	8 Junio 2024
Redis::TimeoutError : Waited 1.0 seconds / Job exception: MiniScheduler::DistributedMutex::Timeout Support e-bug-tracker , ai	11	180	28 Mayo 2025
Failing to connect to redis after fresh install Self-hosting	4	1199	11 Diciembre 2018
Issue with new update: debugging options Self-hosting	16	253	30 Agosto 2024
Redis Error after update Self-hosting	10	2397	4 Abril 2022

Is there a way to change the redis connection timeout?

Temas relacionados