-
Notifications
You must be signed in to change notification settings - Fork 27
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
Conductor.db.type of redis_sentinel is being ignored #16
Comments
Hi @RussellTaylor83 , Thanks for reporting this. As per the configuration, this looks fine. |
I've joined your slack to see if I can help with diagnosing this / testing fixes. Many thanks |
I see this in the logs:
What version of Redis are you using? |
6.2.6, which I thought would be why I don't have HSCAN. We use bitnami helm charts to deploy it so it should be up to date. I don't know though if this is a symptom of the config not being loaded, or the cause of the issue. |
I don't know if it's related, but is sentinel actually supported? Having just read https://orkes.io/content/docs/getting-started/install/orkes-conductor-community it says: Orkes-Queues - Redis-based queues that improve upon dyno-queues and providers higher performance and are built from |
I've had to deploy a redis cluster for now. Has anyone got sentinel working with orkes please? |
If I set redis.queue.type to redis_cluster as per below:
I get this error:
It's the line conductor.queue.type that does it, which I took from https://github.com/orkes-io/orkes-conductor-community/blob/3c89669169e49b3f403608afe55d94f83a6072f9/server/src/main/resources/application.properties Even without that line (presuming it's set to standalone) I'm struggling to get orkes community to run with any version of redis that isn't standalone. How are people doing it please? |
In fact I can get it working, with this config ...
But it throws this exception:
which is because Jedis is configured to run as standalone! Has anyone got this working with something that isn't standalone??? |
I am actually experiencing the exact same issue. I have confirmed everything above in my own local environment. Forgive me if I am using the terminology incorrectly (I am not much of a Java dev), but it seems there is a Spring dependency on JedisPool but there are no beans that can provide JedisPool when using anything but redis_standalone. I am not familiar enough with Spring to know the reason for this, |
Did anyone manage to get redis working with anything but the standalone config? I was hoping to test this using redis_cluster mode |
I have made some changes to allow us to run in Redis Cluster/Sentinel - seems to work now for us. #23 |
I'm trying to run the orkes server, pointing it to a redis sentinel cluster. I am mounting the following in /app/config/config.properties
Below is the output from orkes, grepping for the wording redis:
So I believe I am loading the config fine, but it's still running the standalone Redis configuration. It looks like the default config, despite me attempting to override it and the output messages suggesting I've done that, is still take precedence?
Any ideas please?
The text was updated successfully, but these errors were encountered: