Redis Commands
- A
- B
- Client
-
Cluster
- Cluster-addslots
- Cluster-addslotsrange
- Cluster-bumpepoch
- Cluster-count-failure-reports
- Cluster-countkeysinslot
- Cluster-delslots
- Cluster-delslotsrange
- Cluster-failover
- Cluster-flushslots
- Cluster-forget
- Cluster-getkeysinslot
- Cluster-help
- Cluster-info
- Cluster-keyslot
- Cluster-links
- Cluster-meet
- Cluster-myid
- Cluster-myshardid
- Cluster-nodes
- Cluster-replicas
- Cluster-replicate
- Cluster-reset
- Cluster-saveconfig
- Cluster-set-config-epoch
- Cluster-setslot
- Cluster-shards
- Cluster-slaves
- Cluster-slots
- Cluster
- Command
- Config
- D
- E
- F
- G
- H
- I
- K
- L
- M
- O
- P
- Q
- R
- S1
- S2
- T
- U
- W
- X
- Z1
- Z2
Docs > Redis Commands > S2 > Ssubscribe
Subscribes the client to the specified shard channels.
In a Redis cluster, shard channels are assigned to slots by the same algorithm used to assign keys to slots.
Client(s) can subscribe to a node covering a slot (primary/replica) to receive the messages published.
All the specified shard channels needs to belong to a single slot to subscribe in a given SSUBSCRIBE
call,
A client can subscribe to channels across different slots over separate SSUBSCRIBE
call.
For more information about sharded Pub/Sub, see Sharded Pub/Sub.
@return
When successful, this command doesn't return anything. Instead, for each shard channel, one message with the first element being the string "ssubscribe" is pushed as a confirmation that the command succeeded. Note that this command can also return a -MOVED redirect.
@examples
> ssubscribe orders
Reading messages... (press Ctrl-C to quit)
1) "ssubscribe"
2) "orders"
3) (integer) 1
1) "smessage"
2) "orders"
3) "hello"