-
Notifications
You must be signed in to change notification settings - Fork 4
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
Added support for redis clustered mode #735
base: master
Are you sure you want to change the base?
Added support for redis clustered mode #735
Conversation
Signed-off-by: munishchouhan <hrma017@gmail.com>
Signed-off-by: munishchouhan <hrma017@gmail.com>
Signed-off-by: munishchouhan <hrma017@gmail.com>
* | ||
* @author Munish Chouhan <munish.chouhan@seqera.io> | ||
*/ | ||
interface RedisService { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure to understand the need for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JedisCluster and JedisPool doesnot have common Interface, so not possible to inject
Thats why I have created this service which have separate implementation for cluster and standalone and based on redis.mode it will be initialized
This reverts commit 31640e4.
Signed-off-by: munishchouhan <hrma017@gmail.com>
We may need to reconsider this, at least in the short run. I was considering a much smaller impact. Also, Platform is not supporting cluster mode for sure, so there's not benefit adding the support for Wave |
we can move further with ssl+auth, which is currently required |
This PR will add support for redis clustered mode