Live data from Hacker News

RethinkDB 2.1 is out: high availability

rethinkdb.com

51–60 of 108 posts

Re: RethinkDB 2.1 is out: high availability

#51

Earlier quoted context omitted.

Yes. We did months of internal tests, and 2.1 passes Jepsen tests. We'd love for Kyle to do his own analysis once he gets some free time. In the meantime there is a bit more info on this in the blog post under "testing" headline.

Based on this pull request: https://github.com/aphyr/jepsen/pull/70 Am I correct in understanding that the tests only pass in the "safe-but-slow" configuration that timmaxw described ( https://news.ycombinator.com/item?id=10043746 ) and not in the default "fast-but-unsafe" configuration?

AFAIK the tests account for that and test different scenarios (i.e. not all unsafe modes are created equal; a product can still fail the relevant test cases in fast-but-unsafe mode). We pass the fast-but-unsafe tests (i.e. we fulfill the guarantees you'd expect in that mode), and also pass the stricter guarantees in the slow-but-safe mode.

However you're right that we don't pass stricter guarantees in fast-but-unsafe mode (but I'm not aware of any products in the space that do).

Re: RethinkDB 2.1 is out: high availability

#52
post #47

This looks awesome .. great job guys .. Just a question on licenses . Server is "GNU Affero General Public License v3.0" and drivers are "Apache License v2.0." , so in simple english does it means that can i use make commercial products with backend as RethinkDB? these things always confuses me so apologies if i ask something stupid here ..

Yes, you can build a commercial product with RethinkDB in the backend without paying us any money; that's explicitly allowed by this licensing scheme.

Re: RethinkDB 2.1 is out: high availability

#54

Earlier quoted context omitted.

Based on this pull request: https://github.com/aphyr/jepsen/pull/70 Am I correct in understanding that the tests only pass in the "safe-but-slow" configuration that timmaxw described ( https://news.ycombinator.com/item?id=10043746 ) and not in the default "fast-but-unsafe" configuration?

AFAIK the tests account for that and test different scenarios (i.e. not all unsafe modes are created equal; a product can still fail the relevant test cases in fast-but-unsafe mode). We pass the fast-but-unsafe tests (i.e. we fulfill the guarantees you'd expect in that mode), and also pass the stricter guarantees in the slow-but-safe mode. However you're right that we don't pass stricter guarantees in fast-but-unsafe…

Good to know. The test code in that pull request only tests the case where read_mode="majority", so I'm looking forward to seeing the other scenarios when they become available.

Re: RethinkDB 2.1 is out: high availability

#55
Very cool, thanks for all the hard work that went into this. Will the docs [1][2] be updated at some point to reflect the Python 3.4.x asyncio support? Right now just Tornado is documented.

[1] http://rethinkdb.com/docs/async-connections/ [2] http://www.rethinkdb.com/api/python/set_loop_type/

Re: RethinkDB 2.1 is out: high availability

#56

Great news! Keep up the good work. It's getting harder and harder to justify not using rethinkdb in production :-) ...Doesn't seem available on homebrew yet though.

We should be able to make it available on brew very soon.

Thanks!

Re: RethinkDB 2.1 is out: high availability

#58

Slava @ RethinkDB here. I'll be around all day to answer questions about the release (along with a few other engineers on our team). We're very excited about this release -- it makes the lives of RethinkDB users dramatically better because they won't have to wake up anymore in the middle of the night in case of most hardware failures :) It also took over a year to build and test, and has been one of the most challeng…

How is the WAN replication performance for a cluster in 3 DCs with ~100-200ms RTT? Or is WAN replication performance on the todo list?

Re: RethinkDB 2.1 is out: high availability

#59

Can I ask please why you don't provide ready to use, fine tunned amazon images? This is preventing me to use it now as I cannot find reliable configuration or information. Also the current image is out of date. Thanks

This article describes deploying on AWS with a pre-built AMI -- http://rethinkdb.com/docs/paas/.

We have an aggressive release cycle and try to release ever 2-4 months. Unfortunately the process to get an image onto AWS is fairly slow (with the exception of security patches). So the AMI images are unfortunately a little behind. We're working hard to update them as soon as possible, but unfortunately most of the process is out of our hands.

Re: RethinkDB 2.1 is out: high availability

#60

Very cool, thanks for all the hard work that went into this. Will the docs [1][2] be updated at some point to reflect the Python 3.4.x asyncio support? Right now just Tornado is documented. [1] http://rethinkdb.com/docs/async-connections/ [2] http://www.rethinkdb.com/api/python/set_loop_type/

Yes, we'll update the docs very soon.
Post reply on HN