Consumer groups concept in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a consumer group in Redis Streams?

A consumer group is a way to allow multiple clients to share the work of processing messages from a Redis Stream. Each consumer in the group gets a subset of messages to process, so the workload is divided.

intermediate

How does Redis ensure that messages are not lost when using consumer groups?

Redis keeps track of which messages each consumer has acknowledged. Messages remain pending until acknowledged, so if a consumer fails, another can claim and process those messages.

beginner

What command creates a consumer group in Redis Streams?

The command is XGROUP CREATE <stream> <groupname> <id>. It creates a new consumer group for the given stream starting at the specified ID.

intermediate

What is the role of the XREADGROUP command?

XREADGROUP lets a consumer read messages from a stream as part of a consumer group. It assigns messages to that consumer and tracks them as pending until acknowledged.

advanced

How can a consumer claim pending messages from another consumer in the same group?

Using the XCLAIM command, a consumer can take ownership of pending messages that were assigned to another consumer but not acknowledged, helping to recover unprocessed messages.

What does a consumer group in Redis Streams help you do?

A Store messages permanently

B Divide message processing among multiple consumers

C Encrypt messages automatically

D Send messages to external databases

Consumer groups allow multiple consumers to share the work of processing messages from a stream.

Which command creates a consumer group in Redis?

A XACK

B XREADGROUP

C XGROUP CREATE

D XCLAIM

XGROUP CREATE is used to create a new consumer group.

What happens to messages in a consumer group before they are acknowledged?

A They are marked as pending

B They are deleted immediately

C They are sent to all consumers

D They are ignored

Messages remain pending until a consumer acknowledges them.

Which command lets a consumer read messages as part of a consumer group?

A XDEL

B XGROUP CREATE

C XADD

D XREADGROUP

XREADGROUP reads messages assigned to a consumer in a group.

How can a consumer recover messages that another consumer did not acknowledge?

A Using XCLAIM

B Using XADD

C Using XGROUP CREATE

D Using XREAD

XCLAIM lets a consumer claim pending messages from others.

Explain how consumer groups help distribute message processing in Redis Streams.

Think about how a team divides tasks to work faster.

Describe the lifecycle of a message in a Redis Stream when using consumer groups.

Follow the message from arrival to processing and acknowledgment.

Practice

1. What is the main purpose of Redis consumer groups in streams?

easy

A. Allow multiple clients to read the same stream without duplicating work

B. Store data permanently in Redis

C. Encrypt messages in the stream

D. Automatically delete old messages from the stream

Solution

1. Step 1: Understand consumer groups role

   Consumer groups let many clients read from the same stream safely and efficiently.

2. Step 2: Identify main benefit

   They avoid duplicate processing by tracking which messages each consumer has read.

3. Final Answer:

   Allow multiple clients to read the same stream without duplicating work -> Option A

4. Quick Check:

   Consumer groups = safe multi-client reading [OK]

Hint: Consumer groups = shared reading without duplicates [OK]

Common Mistakes:

• Thinking consumer groups store data permanently
• Confusing consumer groups with encryption
• Assuming consumer groups delete old messages automatically

2. Which Redis command is used to create a consumer group for a stream named mystream?

easy

A. XGROUP NEW mystream mygroup $

B. XGROUP CREATE mystream mygroup $

C. XGROUP ADD mystream mygroup $

D. XREADGROUP CREATE mystream mygroup $

Solution

1. Step 1: Recall command to create consumer group

   The correct command is XGROUP CREATE followed by stream name, group name, and ID.

2. Step 2: Match command syntax

   XGROUP CREATE mystream mygroup $ correctly creates group mygroup on mystream.

3. Final Answer:

   XGROUP CREATE mystream mygroup $ -> Option B

4. Quick Check:

   Create group = XGROUP CREATE [OK]

Hint: Use XGROUP CREATE to make groups [OK]

Common Mistakes:

• Using XREADGROUP instead of XGROUP CREATE
• Using non-existent commands like XGROUP ADD or XGROUP NEW
• Mixing command order or missing parameters

3. Given a consumer group mygroup on stream mystream, what does this command return?

XREADGROUP GROUP mygroup consumer1 COUNT 2 STREAMS mystream > 

medium

A. Returns up to 2 new messages never delivered to any consumer

B. Returns all messages in the stream from the beginning

C. Returns the last 2 messages already acknowledged

D. Returns an error because of wrong syntax

Solution

1. Step 1: Understand XREADGROUP with '>' ID

   Using '>' means read only new messages never delivered to any consumer in the group.

2. Step 2: COUNT 2 limits messages returned

   The command returns up to 2 such new messages for consumer1.

3. Final Answer:

   Returns up to 2 new messages never delivered to any consumer -> Option A

4. Quick Check:

   XREADGROUP with '>' = new messages only [OK]

Hint: '>' ID in XREADGROUP means new messages only [OK]

Common Mistakes:

• Thinking it returns all messages from start
• Assuming it returns acknowledged messages
• Believing the command syntax is incorrect

4. You run this command but get an error:

XREADGROUP GROUP mygroup consumer1 STREAMS mystream >

What is the likely cause?

medium

A. Missing COUNT argument causes syntax error

B. The '>' symbol is invalid here

C. The command is missing the ID after STREAMS

D. Consumer group 'mygroup' does not exist

Solution

1. Step 1: Verify command syntax

   The syntax is correct: XREADGROUP GROUP mygroup consumer1 STREAMS mystream > uses '>' ID for new messages. COUNT is optional.

2. Step 2: Identify prerequisite error

   XREADGROUP requires an existing consumer group created with XGROUP CREATE. If missing, it returns a NOGROUP error.

3. Final Answer:

   Consumer group 'mygroup' does not exist -> Option D

4. Quick Check:

   XREADGROUP needs existing group [OK]

Hint: XREADGROUP requires existing consumer group [OK]

Common Mistakes:

• Thinking COUNT is mandatory (it's optional)
• Believing '>' is invalid
• Mistakenly thinking ID is missing after STREAMS

5. You have a stream orders and consumer group ordergroup. You want to ensure that if a consumer crashes before acknowledging messages, another consumer can claim and process those pending messages. Which Redis command helps you do this?

hard

A. XREADGROUP GROUP ordergroup consumer2 STREAMS orders >

B. XACK orders ordergroup 1526985058136

C. XCLAIM orders ordergroup consumer2 60000 1526985058136

D. XGROUP CREATE orders ordergroup $

Solution

1. Step 1: Understand the problem of crashed consumers

   If a consumer crashes, its pending messages remain unacknowledged and need to be claimed by others.

2. Step 2: Identify command to claim pending messages

   XCLAIM lets another consumer take ownership of pending messages after a timeout.

3. Step 3: Match command usage

   XCLAIM orders ordergroup consumer2 60000 1526985058136 claims message ID 1526985058136 for consumer2.

4. Final Answer:

   XCLAIM orders ordergroup consumer2 60000 1526985058136 -> Option C

5. Quick Check:

   Claim pending messages = XCLAIM [OK]

Hint: Use XCLAIM to recover unacknowledged messages [OK]

Common Mistakes:

• Using XACK which only acknowledges, not claims
• Using XREADGROUP with '>' which reads new messages only
• Trying to create group again instead of claiming