I’m stuck on Stage 13. I’ve tried created a handshake with master node. The test passes a few times. What I can see is that before a SET command can come to replica node a GET command is called that returns nil as response. I made sure to add a lock on getter and setter of my cache. I cannot find a…

The issue could be related to the reply you get after PSYNC… sometimes its comes out like this: +FULLRESYNC 75cd7bc10c49047e0d163660f3b90625b1af31dc 0\r\n$88\r\nREDIS0011\xfa\tredis-ver\x057.2.0\xfa\nredis-bits\xc0@\xfa\x05ctime\xc2m\b\xbce\xfa\bused-mem°\xc4\x10\x00\xfa\baof-base\xc0\x00\xff\xf0n;…

I’m stuck on the same issue. I have the same problem with GET commands possibly being called before SET commands. Stage 12 went through without any issues, and locally it seams to be working fine. Here is my repo: https://github.com/naqet/naqet-codecrafters-redis-go .

@NexFlare / @naqet there’s a 500ms sleep between each retry there, and we’re retrying 5 times, so that’s 2.5 seconds in total - the tester assumes that should be sufficient time to have received the SET command. I wonder if there’s an issue with a lock not being released? Can you try adding logs ar…

Same issue here. I didn’t use channels or any intentional blocking so far, And just like @naqet all things went well until now, and locally i can’t reproduce the scenario in the test. After running the tests multiple times i noticed that it is definitely a race condition, in most cases the replica m…

I used sync.Map as database for simplicity, so there shouldn’t be any issues with locks as far as I know.

Ah, yep this can be one cause here. The response to PSYNC, the RDB file and the propagated commands can be received all at once. This is because there’s no “wait” step (like waiting for a response) in between - so even though they’re sent “one by one”, we can’t know if your program received them and…

@rohitpaulk i see that in stage 13, in tests the master is not booted in the same way as in tests of stage 12. i added some extra logging and they just don’t show, however they appear in stage 12 tests (See screenshots) . Are we supposed to block only the replica commands(like GET foo) while the han…

This is test 12 output with extra logs at the start [Screenshot 2024-04-18 at 22.41.41]

Hey @remuspoienar , I understand this can be hard to debug, we’re actively thinking of ways to make our logs + instructions better. Hopefully once we’ve figured this out we’ll be able to make the experience smoother for others :slightly_smiling_face: The test doesn’t seem to be using my code for t…

Thanks @rohitpaulk Unfortunately im out of options so i ll just switch to another track, because locally all this works, and managed to connect 3 replicas and they all get propagated commands and have it ready for redis clients. For me this was an issue with the test, because I already pass the rep…

That is a great observation. I looked into this and it seems to have solved the problem. :grinning:

Replication (#YG4) GET commands received before SET?

Challenges

system June 4, 2024, 5:41am 18

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
Redis Challenge: Stuck on Command Processing Challenges challenge:redis	5	249	October 4, 2024
[Gleam] Stuck on Redis Challenge, Replication, Stage 13 Challenges challenge:redis	2	128	June 5, 2024
Replication (#YG4) Unclear that multiple commands can be received at once Challenges challenge:redis	12	474	June 4, 2024
Redis Challenge Stage #YG4: only some set commands reach replica (Go) Challenges challenge:redis	7	269	October 4, 2024
Replica doesn't get replication command - #YG4 test Challenges challenge:redis	2	88	March 29, 2025

Replication (#YG4) GET commands received before SET?

Related topics