Skip to content
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

Configure redis in connection factory as read only or read&write and test it [DATAREDIS-319] #895

Closed
spring-projects-issues opened this issue Jun 26, 2014 · 1 comment
Assignees
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement

Comments

@spring-projects-issues
Copy link

spring-projects-issues commented Jun 26, 2014

Greg Dubicki opened DATAREDIS-319 and commented

I would be much safer to use spring data redis in multiple redises environment, with both masters and read-only slaves, with possibility to configure the connection factory as "read only" or "read & write".

To make this setting work spring data redis would have to make a test when creating the connection factory if this redis is in fact read only or read&write.

It could make a test SET operation with random key with "spring-data-redis-" prefix for safety and check for read only exception. It exception would not be recieved a DEL to clean up would be performed.

Of cource the result of this test would be used to continue running or throw an exception if inapproprate type of connection factory would be set for this redis

Rationale: We use this kind of environment and have had some problems with using read only redis by mistake in connection factory that we later used for read&write. The key word here is "later" - if above implementation would be included we would learn about our mistake just after running the application. Our problem was that the write operations came some time after starting it, long after we had stopped watching the logs..


Issue Links:

  • DATAREDIS-580 Support Master/Slave connections using Lettuce
    ("is superseded by")
@spring-projects-issues
Copy link
Author

spring-projects-issues commented Apr 6, 2020

Mark Paluch commented

This issue is superseded by DATAREDIS-580 which introduced dedicated support for replication arrangements (Static Master/Replica, Sentinel, Redis Cluster)

@spring-projects-issues spring-projects-issues added status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement labels Dec 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants