4 ms·
Those defaults were changed a decade ago and were never an issue if you used a driver eg. Python. And the Jepsen tests are part of the core test suite so do yo
by threeseed 5y ago
Those defaults were changed a decade ago and were never an issue if you used a driver eg. Python.
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.
- dralley 5y agoPerhaps, but mongodb was responsible for something I have bookmarked as "the worst line of code ever". Which decided whether or not to log connection warnings based on Math.random() https://github.com/mongodb/mongo-java-driver/blob/1d2e6faa80aeb5287a26d0348f18f4b51d566759/src/main/com/mongodb/ConnectionStatus.java#L212-L215 https://github.com/mongodb/mongo-java-driver/blob/1d2e6faa80...
- threeseed 5y agoa) 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. [1] https://jira.mongodb.org/browse/JAVA-836 https://jira.mongodb.org/browse/JAVA-836
- __turbobrew__ 5y agohttps://github.com/mongodb/mongo-java-driver/commit/d51b3648a8e1bf1a7b7886b7ceb343064c9e2225#diff-a4601c990f57148121efae9587a61e61afb4b7eb3f1f5537ad5aded607c5a0c3R212 https://github.com/mongodb/mongo-java-driver/commit/d51b3648...