Hi All, Need help in debugging this stage (replication -11). I am able to individually run a master, replica and connect with redis-cli clients to the master to watch the logs on the replication. The tester program expecting some output which I am not able to figure out, the logs are so general. A…

Logs should now include more details like “Expecting commands to be propagated”. We’re also going to work on splitting logs into multiple stages (handshake, propagation etc.). Will close for now and wait for similar reports before we make further changes here!

This is no longer a blocker, was able to fix it. I had used same variable name for writing into client sockets ( both clients connecting to server, also writing to replica’s) I still need to refactor the code in a better way so that these issues can be debug The error message from the tester shoul…

[image] Jothikumar-ekanath: e to fix it. I had used same variable name for writing into client sockets ( both clients connecting to server, also writing to replica’s) I still need to refactor the code in a better way so that these issues can be debug The error message from the tester shou H…

The error message given by the tester is so generic, it will hard to debug. Please post the complete error log and code. I can try to debug. I had a bug in my code where I used the same variable name for both master writing to clients and master replicating the set commands to replicas. once I fixe…

Thanks for responding. It looks like I have passed this stage after making multiple changes in my code. As you say, the error given is so generic and makes it really hard to debug. Also, you mentioned the complete error log, do you mean that you can see some sort of detailed error log somewhere in …

yes, It is hard to debug just using tester’s console output. Please add more print statements in your code. Along with your print statements and the testers console log output it will eventually become easier to debug Complete error log, I meant the console output when you run the tests.

We’re adding logs here to make it more clear what the tester expects. Will keep this open until that’s done!

Stuck on replication #ZN8

Challenges

system June 4, 2024, 3:29am 8

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

Topic		Replies	Views
SOLVED: issue with Single-replica propagation stage #ZN8 Challenges challenge:redis	5	388	June 4, 2024
Go Redis Replication #NA2 Challenges challenge:redis	4	347	December 18, 2024
Replication #ZN8: Feedback with more detail on problem? Challenges challenge:redis	8	318	June 4, 2024
Stuck in replication #NA2 Challenges challenge:redis	13	295	June 4, 2024
Replication Stage #YD3 Missing GEKACK Challenges challenge:redis	2	182	June 4, 2024

Stuck on replication #ZN8

Related topics