@cockroachdb Very interested in @aphyr's take on this, or from some similar such person who's not part of the company
-
-
-
@elimisteve Aphyr gave us some early feedback on the post. You can read the twitter thread here:https://twitter.com/cockroachdb/status/720657715106721794 …
End of conversation
New conversation -
-
-
small typo 'Additional gratitude is owed to Aphry'
-
Fixed! Good eye on that one.
End of conversation
New conversation -
-
-
@cockroachdb@aphyr Good tips. Thanks. Scheduling longer runs is definitely on the agenda, we plan to dedicate some resources to this. -
@kena42@cockroachdb It's a terrific write up, thank you! -
@aphyr@cockroachdb Well thanks to you sir for your amazing work.
End of conversation
New conversation -
-
-
@cockroachdb ahhhh good catch on the reconnect logic, that was a real hassle to write and I am not at all surprised I made a mistake. -
@cockroachdb jdbc threading and conn management is a real bear to reason about. If you can think of a good generalizable soln, PR plz! -
@cockroachdb You may also want to run for longer durations; often takes a few thousand seconds to hit a failure. Galera tests fail quick.
End of conversation
New conversation -
-
-
@cockroachdb@aphyr in your experience, which tests are more likely to fail only after a long while? -
@kena42@cockroachdb all of em, really. Usually takes a few weeks to get a failure. Then I narrow in on the issue and test time drops. -
@kena42@cockroachdb if I'm really lucky it fails right off the bat. I think aerospike was one of those. Percona/galera took a while.
End of conversation
New conversation -
-
-
@cockroachdb awesome. First thing I did when I saw your announcement was ask@aphyr if he'd looked at it. I hope you work w/him for more!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.