REPLICAOF command in Redis - Step-by-Step Execution

Concept Flow - REPLICAOF command

Start Redis Instance

↓

Issue REPLICAOF host port

↓

Connect to Master at host:port

↓

Synchronize Data from Master

↓

Apply Updates from Master

↓

Serve Read Requests as Replica

↓

If REPLICAOF NO ONE

↓

Stop Replication, Become Master

The REPLICAOF command connects a Redis instance to a master to replicate data, syncing and applying updates continuously. Using 'NO ONE' stops replication.

Execution Sample

Redis

REPLICAOF 192.168.1.10 6379
REPLICAOF NO ONE

This sets the current Redis instance to replicate from the master at 192.168.1.10:6379, then stops replication to become master.

Execution Table

Step	Command	Action	Result	State Change
1	REPLICAOF 192.168.1.10 6379	Connect to master at 192.168.1.10:6379	Connection established	Instance becomes replica
2	Synchronize data	Copy data from master	Data synced	Replica data matches master
3	Apply updates	Receive and apply master's updates	Data stays current	Replica data updated continuously
4	Serve read requests	Accept client reads	Reads served from replica	Replica serves read-only
5	REPLICAOF NO ONE	Stop replication	Replication stopped	Instance becomes master
6	Serve read/write requests	Accept client reads and writes	Reads and writes served	Instance acts as master
7	End	No further commands	Idle	State stable as master

💡 Replication stops when REPLICAOF NO ONE is issued, instance becomes master.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 5	Final
Role	master	replica	replica	replica	master	master
Connection to Master	none	connected	connected	connected	disconnected	none
Data State	own data	syncing	synced	updated	own data	own data
Accept Writes	yes	no	no	no	yes	yes

Key Moments - 3 Insights

Why does the instance stop accepting writes after REPLICAOF to a master?

Because after REPLICAOF, the instance becomes a replica and only serves read requests, as shown in execution_table rows 1 to 4.

What happens when you issue REPLICAOF NO ONE?

The instance stops replicating and becomes a master again, accepting writes, as shown in execution_table row 5.

Does the replica immediately have all data from the master after REPLICAOF?

No, it first synchronizes data (row 2), then applies updates continuously (row 3).

Visual Quiz - 3 Questions

Look at the execution_table, what is the Role of the instance after Step 3?

A replica

B master

C disconnected

D unknown

💡 Hint

Check the 'Role' variable in variable_tracker after Step 3.

At which step does the instance stop replicating and become master again?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look for the REPLICAOF NO ONE command in execution_table.

If you never issue REPLICAOF NO ONE, what will the instance's Accept Writes state be?

A yes

B no

C sometimes

D depends on master

💡 Hint

See variable_tracker Accept Writes column before Step 5.

Concept Snapshot

REPLICAOF host port
- Connects Redis instance as replica to master at host:port
- Syncs data and applies updates continuously
- Replica serves read-only requests
REPLICAOF NO ONE
- Stops replication
- Instance becomes master again
- Accepts reads and writes

Full Transcript

The REPLICAOF command in Redis sets the current instance to replicate data from a specified master by connecting to its host and port. After issuing REPLICAOF, the instance synchronizes data from the master and applies updates continuously, serving read requests only. When REPLICAOF NO ONE is issued, replication stops and the instance becomes a master again, accepting both reads and writes. This flow ensures data consistency and allows flexible role changes between master and replica.