4 ms·

No not using Jepsen. I've written custom tests in GO running thousands of concurrent client connections on local and remote clusters with multiple nodes and no

No not using Jepsen. I've written custom tests in GO running thousands of concurrent client connections on local and remote clusters with multiple nodes and node replicas I test consistency, crisis, recovery, etc. The database hasn't shown me personally any flaws whatsoever. Anyone can go ahead and write their own Jepsen tests if they please.

alexpadula 3y ago
Maybe down the line if people REALLY want it I'll do it but I think I'll just post my tests instead. The thing is I'd rather make a video as you can't test power outages and so forth with just a script. I've done this using hardware locally and I can't find flaws. I'm not trying to make it seem any which way. I'd rather have more people write their own tests as well, why not!
- jwr 3y ago
  Well, Jepsen has a reputation for finding problems in pretty much every database they test and has become a sort of a benchmark by now. Many people (including myself) won't consider a distributed database if it hasn't been put through Jepsen. The only exception I know of is FoundationDB, which was written pretty much test-first, and about which Kyle Kingsbury said that their tests are likely better :-)
  - alexpadula 3y ago
    Thank you for the information @jwr! I've looked into it. I'm not trying to put money down on anything currently. I've tested, and I mean tested hundreds of hours possibly even thousands from the start to the now, every feature, multiple ways. I wouldn't deploy releases and mention features as an actual feature if I didn't test every single thing beforehand. I am thorough, I do crazy amounts of sanity checks on everything, I don't just claim things. I myself cannot do everything in the span of not even 60 days except test everything as I went on and continue to. I post about it on the Github. CursusDB must be manually and driven tested. Very easy to automate but very easy to miss steps. Thank you for your response.
    - alexpadula 3y ago
      To add, I'm not saying I wont do it. I just don't have funds for it currently. I'll save up and make sure to get it completed for the sanity of the many like you :D As stated previously I truly on every aspect test every method before implementation, I test features, I test REAL failures and scenarios like actually having a box running and power shutting down during a large transaction on nodes,I'm saying not virtually actually shutting power down and seeing if the system can persist. I did a lot and continue to for my own confidence. If it's not enough for you and others I do completely understand your reasoning hence mine to save for the Jepsen.

alexpadula 3y ago

Maybe down the line if people REALLY want it I'll do it but I think I'll just post my tests instead. The thing is I'd rather make a video as you can't test power outages and so forth with just a script. I've done this using hardware locally and I can't find flaws. I'm not trying to make it seem any which way. I'd rather have more people write their own tests as well, why not!

jwr 3y ago
Well, Jepsen has a reputation for finding problems in pretty much every database they test and has become a sort of a benchmark by now. Many people (including myself) won't consider a distributed database if it hasn't been put through Jepsen. The only exception I know of is FoundationDB, which was written pretty much test-first, and about which Kyle Kingsbury said that their tests are likely better :-)
- alexpadula 3y ago
  Thank you for the information @jwr! I've looked into it. I'm not trying to put money down on anything currently. I've tested, and I mean tested hundreds of hours possibly even thousands from the start to the now, every feature, multiple ways. I wouldn't deploy releases and mention features as an actual feature if I didn't test every single thing beforehand. I am thorough, I do crazy amounts of sanity checks on everything, I don't just claim things. I myself cannot do everything in the span of not even 60 days except test everything as I went on and continue to. I post about it on the Github. CursusDB must be manually and driven tested. Very easy to automate but very easy to miss steps. Thank you for your response.
  - alexpadula 3y ago
    To add, I'm not saying I wont do it. I just don't have funds for it currently. I'll save up and make sure to get it completed for the sanity of the many like you :D As stated previously I truly on every aspect test every method before implementation, I test features, I test REAL failures and scenarios like actually having a box running and power shutting down during a large transaction on nodes,I'm saying not virtually actually shutting power down and seeing if the system can persist. I did a lot and continue to for my own confidence. If it's not enough for you and others I do completely understand your reasoning hence mine to save for the Jepsen.