You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/commands/spublish/index.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -52,14 +52,14 @@ title: SPUBLISH
52
52
Posts a message to the given shard channel.
53
53
54
54
In Redis Cluster, shard channels are assigned to slots by the same algorithm used to assign keys to slots.
55
-
A shard message must be sent to a node that own the slot the shard channel is hashed to.
56
-
The cluster makes sure that published shard messages are forwarded to all the node in the shard, so clients can subscribe to a shard channel by connecting to any one of the nodes in the shard.
55
+
A shard message must be sent to a node that owns the slot the shard channel is hashed to.
56
+
The cluster makes sure that published shard messages are forwarded to all the nodes in the shard, so clients can subscribe to a shard channel by connecting to any one of the nodes in the shard.
57
57
58
58
For more information about sharded pubsub, see [Sharded Pubsub]({{< relref "/develop/interact/pubsub#sharded-pubsub" >}}).
59
59
60
60
## Examples
61
61
62
-
For example the following command publish to channel`orders` with a subscriber already waiting for message(s).
62
+
For example the following command publishes to the`orders` channel with a subscriber already waiting for message(s).
0 commit comments