Comments (3)
Seems like we are indeed using CLUSTER NODES
, which currently is against the recommendation in the docs:
Note that normally clients willing to fetch the map between Cluster hash slots and node addresses should use CLUSTER SLOTS instead. CLUSTER NODES, that provides more information, should be used for administrative tasks, debugging, and configuration inspections. It is also used by redis-cli in order to manage a cluster.
This was initially implemented a while ago in #240 (Lettuce 4.2.0) and seems to have never been addressed since.
The change does not require new design, but has impact on large portions of the code.
Adding to the backlog until we have spare resources.
from lettuce.
I've been poking around a bit, it doesn't seem that risky, at least at first glance. What do you think about a new contributor (me) trying to tackle this?
Absolutely, feel free to submit a PR, you are more than welcome.
from lettuce.
I've been poking around a bit, it doesn't seem that risky, at least at first glance. What do you think about a new contributor (me) trying to tackle this?
from lettuce.
Related Issues (20)
- After turning on topology refresh, lettuce log is written inside rocketmq-client.log. HOT 4
- Lettuce client reconnecting frequently HOT 1
- Custom command with Lettuce occurs UnsupportedOperationException HOT 1
- Stateful redis cluster pubsub is not working HOT 4
- Why does lecttuce send lua script load command to all nodes (including replicas) in redis cluster? HOT 4
- `DefaultClientResources.dnsResolver(DnsResolver resolver)` should be marked as deprecated.
- ClusterTopologyChangedEvent Timing Issue
- Provide a convenience method to support reading of last message from stream
- use with gateway,but something throw io.lettuce.core.output.ValueOutput does not support set(long) HOT 10
- Adjusting disconnectedBehavior Option to Prevent Timeout When Redis Shutdown HOT 4
- Pool exhausted, Java 21 and Virtual Threads HOT 3
- AWS RedisCache replica Failover can not be resolved HOT 1
- Release Lettuce 7.0.0.RELEASE
- Thread blocked when using one global instance of ClientResources but repeatedly opening and closing connections HOT 1
- Prepare 6.4.0 branch
- Application got io.lettuce.core.RedisCommandTimeoutException irregularly. HOT 3
- Caused by: io.lettuce.core.RedisCommandExecutionException: NOAUTH Authentication required. HOT 3
- BugReport: ClusterTopologyRefreshTask is not shutdown when RedisClusterClient is shutdown
- Deadlock in SharedLock HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lettuce.