I’m stuck on stage 18 replication. My approach is to send a GETACK '*' command to each replica and update some form of counter while the timeout is not yet expired or the number of expected replicas are yet to be met. While I’m unable to meet the expected outcome (due to whatever reason), I notice…

@9jaswag In the loop above, after the rescue block triggers I think the loop will just continue (it’ll move on the next element). Could that explain why you aren’t hitting the error log below the each block?

Hi @rohitpaulk , There are a few other topics related to not getting a response when REPLCONF GETACK * is sent to a replica. Any help regarding this will be appreciated :pray:

Hey @9jaswag ! Yep, this does seem to be a common point of confusion. We’re going to update the instructions here. In this stage, it is expected that some replicas will not send ACKs back (that’s what we’re testing – whether your program can accurately identify replicas which did send ACKs vs. ones …

In my case, I get an Errno::ECONNRESET error. Does getting this error mean the replica didn’t acknowledge the previous command? From my understanding from previous stages, I would expect a reply with an offset of 0 or so to mean the last command wasn’t acknowledged. Is this assumption incorrect?

In my case, I get an Errno::ECONNRESET error. Does getting this error mean the replica didn’t acknowledge the previous command? From my understanding from previous stages, I would expect a reply with an offset of 0 or so to mean the last command wasn’t acknowledged. Is this assumption incorrect? …

Catching the Errno::ECONNRESET error doesn’t work and returns this output: [replication-18] client: $ redis-cli WAIT 3 500 [replication-18] Received: "" (no content received) [replication-18] ^ error [replication-18] Error: Expected start of a new RESP value (either +, -, :, $ or *) [rep…

@9jaswag After catching the error, can you log out the bytes that you’re sending back to the client? The logs suggest that no response was received. If you could send a small code snippet, that’d be useful for us to look through too!

@rohitpaulk I agree with you. It seems as though as soon as the error occurs, code execution is terminated and then nothing is returned to the client from my redis server (hence why I asked if there was some form of error suppression or if I was doing something wrong). here’s a snippet of my code a…

@rohitpaulk any thoughts on this?

Closing this for now, please do let us know if you still need help!

Ruby: Redis Replication Stage #NA2: Error reading replica acknowledgement

Challenges

system June 4, 2024, 2:23am 15

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

Topic		Replies	Views
Rust Reids Replication (#NA2) Connection reset by peer (os error 104) Challenges challenge:redis	3	264	June 4, 2024
Replication Stage #YD3 Missing GEKACK Challenges challenge:redis	3	181	June 4, 2024
Replication stage 15 Challenges challenge:redis	4	143	June 3, 2024
Stuck at redis #NA2 Challenges challenge:redis	2	103	July 15, 2024
Go Redis Replication #NA2 Challenges challenge:redis	5	338	December 18, 2024

Ruby: Redis Replication Stage #NA2: Error reading replica acknowledgement

Related topics