1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
It looks like redis cli issue. Here are few recommendations for running bigkeys and hotkeys:
-
Use the latest stable redis cli release: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/nodes-connecting.html
-
Use redis-cli connect to the configuration endpoint. Configuration endpoint could be found from cluster details.
-
Find the **primary nodes **by executing cluster nodes.
$ redis6-cli -c -h <configuration endpoint> -p 6379 --tls
cluster nodes
- Run the bigkeys and hotkeys against the node endpoint of individual primary nodes.
$ redis6-cli -c -h <primary node endpoint> -p 6379 --tls --hotkeys
answered a year ago
Relevant content
- asked 5 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
For all my tests I'm using the configuration endpoint. I will test the primary node endpoint recommendation
Well, with the cluster mode enabled, there is no concept of primary node endpoint. Based on the following documentation: Redis (cluster mode enabled) clusters with replicas, because they have multiple shards (API/CLI: node groups), which mean they also have multiple primary nodes, have a different endpoint structure than Redis (cluster mode disabled) clusters. Redis (cluster mode enabled) has a configuration endpoint which "knows" all the primary and node endpoints in the cluster.