I’m stuck on stage13 - Command Processing. I’ve tried receive as much data as possible from master, but it seems that the master is not send any msg to my replica(6380). Here are my logs: remote: [replication-13] Running tests for Replication > Stage #13: Command Processing remote: [replication-1…

Thank you for the reply. The issue has been resolved; it was caused by not using another thread to execute the slave.

Similar to this issue: [image] Replication 13 - Unclear that multiple commands can be received at once Challenges Facing a similar issue, my instance is not receiving some bytes from the server [Screenshot 2024-04-08 at 12.11.21 AM] The RDB file bytes are never received…

Hey @zRains ! Are you still facing issues with this? My guess here is that this means the connection was closed after the handshake, instead of remaining open to receive propagated commands.

Command processing (#YG4) write to broken pipe

Challenges

system June 4, 2024, 5:38am 6

Note: I’ve updated the title of this post to include the stage ID (#YG4). You can learn about the stages rename here: Upcoming change: Stages overhaul

Topic		Replies	Views
Broken Pipeline error help yg4 Challenges challenge:redis	3	105	August 22, 2024
Redis Challenge: Stuck on Command Processing Challenges challenge:redis	6	244	October 4, 2024
Commands propagated but not executed in replica (#YG4) Challenges challenge:redis	12	296	October 8, 2024
Go trouble with replica processing commands Challenges challenge:redis	1	55	February 9, 2025
Command processing stage Challenges challenge:redis	2	97	May 23, 2024

Command processing (#YG4) write to broken pipe

Related topics