I’m stuck on Replication 17. I’ve tried Real Redis MASTER and 1 my Redis As SLAVE. When I sent WAIT 10 300 to the MASTER without any WRITEs before I’ve got: [‘REPLCONF’, ‘GETACK’, ‘*’] on SLAVE and everything works fine. Then I’ve tried my Redis as MASTER and 1 Real Redis SLAVE. When I sent WA…

We’ve got to improve logs here to convey when replicas received GETACKs, and when they send ACKs back (or not). Will keep open until we’ve done this!

Hey @gnomeby , Can you try setting debug: true in your codecrafters.yml? I think you should see more helpful logs in that case. We should be logging out the reciept of GETACK *, and the ACKs that were sent back. More on debug mode here: How do I debug test failures? - CodeCrafters

With debug: remote: [replication-17] client: $ redis-cli WAIT 3 500 remote: [replication-17] client: Sent bytes: "*3\r\n$4\r\nWAIT\r\n$1\r\n3\r\n$3\r\n500\r\n" remote: [your_program] ['WAIT', '3', '500'] remote: [your_program] R <- b'*3\r\n$8\r\nREPLCONF\r\n$6\r\nGETACK\r\n$1\r\n*\r\n' remote:…

I am also running into the same issue. Setting debug: true in the config file shows that the test replica does not respond to the getack commands that I send as the connection is reset. Are there any solutions on my end to this problem? [image]

Here are full logs: remote: [replication-17] client: $ redis-cli WAIT 3 500 remote: [replication-17] client: Sent bytes: "*3\r\n$4\r\nWAIT\r\n$1\r\n3\r\n$3\r\n500\r\n" remote: [your_program] ['WAIT', '3', '500'] remote: [your_program] R <- b'*3\r\n$8\r\nREPLCONF\r\n$6\r\nGETACK\r\n$1\r\n*\r\n'…

Confirming this. I’m having the same problem with stage 17 and being incompatible: Redis Replication 18: Timeout Issue - #5 by malshoff

We’ve now added logs that convey when a replica decides to respond vs. not: [Screenshot 2024-05-13 at 12.52.32] Going to close this out for now, please let us know if you still need help!

In test for the Replication-17 step your replicas are not going to get: REPLCONF GETACK * when master get WAIT cmd. and this is described in Replication-17 step. It is clear and there would not be a problem if real REDIS behaves in the same way. But it is not. Real REDIS sends REPLCONF GETACK * …

@gnomeby our behaviour should match what Redis does. We verify our tester against an official Redis server for this very purpose. Can you share more details on the differences you’re seeing? Are you able to observe this locally?

Yes, I observed this locally when I connect my official Redis 7.2.4 (MASTER) to my python Redis (SLAVE). And I described this in the initial comment.

I’ve rechecked behavior and found the following: Case 1: Official empty Redis as MASTER and 1 my redis as slave if I send WAIT 1 1 to master then MASTER responses immediately without sending REPLCONF GETACK * to SLAVE. if I send WAIT 2 1 (more replicas then exists) to master then MASTER sends R…

Incorrect test for Replication #TU8

Challenges

system June 4, 2024, 2:15am 15

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

Topic		Replies	Views
Clarity on redis: replication #NA2 Challenges challenge:redis	3	256	June 4, 2024
#TU8 replicas not responding to REPLCONF GETACK * Challenges challenge:redis	4	68	March 18, 2025
Redis Challenge #YD3 Challenges challenge:redis	10	190	July 13, 2025
Python Replicas Stage (#NA2) ACK from tester is not sent immediately General	4	133	June 11, 2024
Redis Replication #NA2: timeout before receiving expected number of responses Challenges challenge:redis	10	341	June 12, 2024

Incorrect test for Replication #TU8

Related topics