a) This is a line of code from 2013 and was fixed weeks after.
b) Based on the JIRA [1] it was designed to only log 10% of subsequent failures where there is no connection to prevent log flooding. You would still get the initial failure message.
Pretty reasonable technique and hardly the worst code ever.
And the Jepsen tests are part of the core test suite so do you some evidence they are still failing.
It’s so ridiculous and pointless to be rehashing the same issues a decade later.
Actually more a testament to the company that it’s still hugely successful and depended on by some very large applications.