I'm having problems with tests that include large amount of nodes. The cause is the huge amount of traffic generated by the rumor-mongering mechanism (i.e. acking with status packets, forwarding new rumors, ...) which considerably slows everything down. As a last resort, I used Wireshark to check how the reference nodes managed to cope with such heavy traffic. To my surprise, the amount of messages was very small, and most importantly there seemed to be no status messages and nodes didn't seem to forward any new rumor. To confirm this I tried a simple chain setup (A <-> B <-> C <-> D) where A indexes a file, and indeed the PaxosPropose wasn't forwarded by B and no status was sent as ack.
So I just wanted to know if anyone managed to pass the tests while strictly treating the rumors with extras as any other rumor? If yes, then my implementation is most likely just bad and I'm sorry to have wasted your time. But if others are in the same situation as me then I feel like the tests were calibrated to work with the (optimized, but not following the specs) reference nodes but might not be compatible when run with nodes that strictly follow what was described in the homework handouts.
Thanks in advance for your responses :)