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
We use kubernetes weblate version 4.4.2-1 with external redis host. In our environment redis - is a cluster service with 2 nodes (master + slave). Master host is always known by a cluster DNS A-record, pointing to IP of current active RW redis node.
The problem we have - when redis host changes role master -> slave, weblate does no reconnect to new redis master. It seems weblate resolve REDIS_HOST IP while starting and use it's address further. Restarting weblate fix the problem - it resolves new redis host IP and works fine.
Errors in weblate logs: uwsgi stderr | django_redis.exceptions.ConnectionInterrupted: Redis ReadOnlyError: You can't write against a read only replica.
Do you have any appropriate configuration option in weblate to reconnect + nslookup to redis if request fail? Or may be force doing lookup at any request?
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.
In case your question is already answered, making a donation is the right way to say thank you!
Describe the issue
Hello.
We use kubernetes weblate version 4.4.2-1 with external redis host. In our environment redis - is a cluster service with 2 nodes (master + slave). Master host is always known by a cluster DNS A-record, pointing to IP of current active RW redis node.
The problem we have - when redis host changes role master -> slave, weblate does no reconnect to new redis master. It seems weblate resolve REDIS_HOST IP while starting and use it's address further. Restarting weblate fix the problem - it resolves new redis host IP and works fine.
Errors in weblate logs:
uwsgi stderr | django_redis.exceptions.ConnectionInterrupted: Redis ReadOnlyError: You can't write against a read only replica.
Do you have any appropriate configuration option in weblate to reconnect + nslookup to redis if request fail? Or may be force doing lookup at any request?
I already tried
Steps to reproduce the behavior
Expected behavior
weblate reconnect to new redis master host using the same REDIS_HOST = redis.example.com
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
4.4.2-1
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: