UNSUBSCRIBE behavior in Redis - Step-by-Step Execution

Concept Flow - UNSUBSCRIBE behavior

Client SUBSCRIBED to channels

↓

Client sends UNSUBSCRIBE command

↓

Server removes client from specified channels

↓

Server sends confirmation message for each channel unsubscribed

↓

If no channels specified, unsubscribe from all

↓

Client no longer receives messages from those channels

This flow shows how a client unsubscribes from channels in Redis Pub/Sub, stopping message delivery from those channels.

Execution Sample

Redis

SUBSCRIBE news sports
UNSUBSCRIBE news
UNSUBSCRIBE

Client subscribes to 'news' and 'sports', then unsubscribes from 'news', then unsubscribes from all remaining channels.

Execution Table

Step	Client Command	Channels Affected	Server Action	Server Response	Client Subscription State
1	SUBSCRIBE news sports	news, sports	Add client to 'news' and 'sports'	[subscribe, news, 1], [subscribe, sports, 2]	Subscribed to news, sports
2	UNSUBSCRIBE news	news	Remove client from 'news'	[unsubscribe, news, 1]	Subscribed to sports
3	UNSUBSCRIBE	all remaining	Remove client from all channels	[unsubscribe, sports, 0]	Subscribed to none
4	No more subscriptions	none	No action	No response	Subscribed to none

💡 Client has unsubscribed from all channels, so no more messages will be received.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Subscribed Channels	[]	[news, sports]	[sports]	[]	[]

Key Moments - 3 Insights

Why does the server send a confirmation message after UNSUBSCRIBE?

The server sends a confirmation message (see execution_table step 2 and 3) to inform the client which channel it has unsubscribed from and how many channels remain subscribed.

What happens if UNSUBSCRIBE is called without specifying channels?

If no channels are specified (execution_table step 3), the server unsubscribes the client from all subscribed channels, clearing the subscription list.

Does the client receive messages from unsubscribed channels?

No, after unsubscribing (execution_table step 2 and 3), the client no longer receives messages from those channels.

Visual Quiz - 3 Questions

Look at the execution_table, what is the client's subscription state after step 2?

A Subscribed to none

B Subscribed to news and sports

C Subscribed to sports only

D Subscribed to news only

💡 Hint

Check the 'Client Subscription State' column in execution_table row for step 2.

At which step does the client unsubscribe from all channels?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Channels Affected' and 'Server Action' columns in execution_table.

If the client only subscribed to 'news' and then called UNSUBSCRIBE without arguments, what would be the subscription state after?

A Subscribed to none

B Subscribed to news

C Subscribed to all channels

D Subscribed to sports

💡 Hint

Refer to the behavior in execution_table step 3 where UNSUBSCRIBE without channels clears all subscriptions.

Concept Snapshot

UNSUBSCRIBE command removes client subscriptions.
Specify channels to unsubscribe from those only.
No channels means unsubscribe from all.
Server sends confirmation messages.
Client stops receiving messages from unsubscribed channels.

Full Transcript

The UNSUBSCRIBE command in Redis Pub/Sub lets a client stop receiving messages from channels. When a client sends UNSUBSCRIBE with channel names, the server removes the client from those channels and sends confirmation messages. If no channels are specified, the client is unsubscribed from all channels. This stops message delivery from those channels to the client. The execution table shows a client subscribing to 'news' and 'sports', then unsubscribing from 'news', and finally unsubscribing from all remaining channels. The variable tracker shows how the subscription list changes after each command. Key moments clarify why confirmation messages are sent and what happens when no channels are specified. The visual quiz tests understanding of subscription states at each step.