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

Add CLUSTER SLOT-STATS document. #150

Merged
merged 11 commits into from
Nov 18, 2024
95 changes: 95 additions & 0 deletions commands/cluster-slot-stats.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,95 @@
`CLUSTER SLOT-STATS` returns an array of slot usage statistics for slots assigned to the current shard.
madolson marked this conversation as resolved.
Show resolved Hide resolved
The command is suitable for Valkey Cluster users aiming to assess general slot usage trends, identify hot / cold slots, migrate slots for a balanced cluster workload, and / or re-write application logic to better utilize slots.

The following statistics are supported:
* `key-count` - Number of keys residing in a given slot.
* `cpu-usec` - Amount of cpu time (in micro-seconds) spent on a given slot.
* `network-bytes-in` - Amount of network ingress (in bytes) received for given slot.
* `network-bytes-out` - Amount of network egress (in bytes) sent out for given slot.

## Supported filtering and ordering arguments
There exist two mutually exclusive arguments for controlling the output, namely;

### SLOTSRANGE
Returns slot statistics based on the slots range provided. The range is inclusive.
The `SLOTSRANGE` argument allows for request pagination.
The response is ordered in ascending slot number.
madolson marked this conversation as resolved.
Show resolved Hide resolved

##### Response in RESP2
madolson marked this conversation as resolved.
Show resolved Hide resolved
```
> CLUSTER SLOT-STATS SLOTSRANGE 0 1
1) 1) (integer) 0
2) 1) "key-count"
2) (integer) 0
3) "cpu-usec"
4) (integer) 0
5) "network-bytes-in"
6) (integer) 0
7) "network-bytes-out"
8) (integer) 0
2) 1) (integer) 1
2) 1) "key-count"
2) (integer) 0
3) "cpu-usec"
4) (integer) 0
5) "network-bytes-in"
6) (integer) 0
7) "network-bytes-out"
8) (integer) 0
```

##### Response in RESP3
```
> CLUSTER SLOT-STATS SLOTSRANGE 0 1
1) 1) (integer) 0
2) 1# "key-count" => (integer) 0
2# "cpu-usec" => (integer) 0
3# "network-bytes-in" => (integer) 0
4# "network-bytes-out" => (integer) 0
2) 1) (integer) 1
2) 1# "key-count" => (integer) 0
2# "cpu-usec" => (integer) 0
3# "network-bytes-in" => (integer) 0
4# "network-bytes-out" => (integer) 0
```

### ORDERBY
The `ORDERBY` argument returns an ordered slot statistics based on the specified statistic and sub-arguments to identify hot / cold slots across the cluster. In the event of a tie in the stats, ascending slot number is used as a tie breaker.

##### Response in RESP2
```
> CLUSTER SLOT-STATS ORDERBY KEY-COUNT LIMIT 2 DESC
madolson marked this conversation as resolved.
Show resolved Hide resolved
1) 1) (integer) 12426
2) 1) "key-count"
2) (integer) 45
3) "cpu-usec"
4) (integer) 0
5) "network-bytes-in"
6) (integer) 0
7) "network-bytes-out"
8) (integer) 0
2) 1) (integer) 13902
2) 1) "key-count"
2) (integer) 20
3) "cpu-usec"
4) (integer) 0
5) "network-bytes-in"
6) (integer) 0
7) "network-bytes-out"
8) (integer) 0
```

##### Response in RESP3
```
> CLUSTER SLOT-STATS ORDERBY KEY-COUNT LIMIT 2 DESC
madolson marked this conversation as resolved.
Show resolved Hide resolved
1) 1) (integer) 12426
2) 1# "key-count" => (integer) 45
2# "cpu-usec" => (integer) 0
3# "network-bytes-in" => (integer) 0
4# "network-bytes-out" => (integer) 0
2) 1) (integer) 13902
2) 1# "key-count" => (integer) 20
2# "cpu-usec" => (integer) 0
3# "network-bytes-in" => (integer) 0
4# "network-bytes-out" => (integer) 0
```