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
I am currently trying to deploy hydra on kubernetes so , I have been trying to make it work with redis in high availability modes.
First the redis sharding or the cluster mode
There is a problem using this mode with hydra since the SELECT command in this mode is disabled because the cluster mode does not support multi databases.
Second mode is the master-slave mode
The problem here is that I have 2 kubernetes services one for the master and the other for the slaves so , the problem is hydra config does not accept a write/read url or readonly url
so we can optimize how it's working with the master-slave mode.
I don't know which of them is the easiest but I would suggest to allow the redis configs to take 2 redis urls which is a master url and a slave url and use the slave for readonly operations.
that would ease out solving the problem in the master-slave mode.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
abdoolly
changed the title
Hydra on kubernetes is not dealing well with redis cluster mode or master-slave mode
Hydra on kubernetes is not working well with redis cluster mode or master-slave mode
Sep 17, 2019
I am currently trying to deploy hydra on kubernetes so , I have been trying to make it work with redis in high availability modes.
First the redis sharding or the cluster mode
There is a problem using this mode with hydra since the SELECT command in this mode is disabled because the cluster mode does not support multi databases.
Second mode is the master-slave mode
The problem here is that I have 2 kubernetes services one for the master and the other for the slaves so , the problem is hydra config does not accept a write/read url or readonly url
so we can optimize how it's working with the master-slave mode.
I don't know which of them is the easiest but I would suggest to allow the redis configs to take 2 redis urls which is a master url and a slave url and use the slave for readonly operations.
that would ease out solving the problem in the master-slave mode.
Thanks in advance.
The text was updated successfully, but these errors were encountered: