Live data from Hacker News

RethinkDB 2.1 is out: high availability

rethinkdb.com

1–10 of 108 posts

Re: RethinkDB 2.1 is out: high availability

#2
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 challenging engineering problems we ever had to solve.

Re: RethinkDB 2.1 is out: high availability

#4
post #3

@coffeemug, do you have an ETA on when performance benchmarks will be released?

This is totally my fault. I've had a pretty comprehensive benchmark report pdf sitting in my inbox for a few months now that the performance team put together, but something else always took my attention away. I'll ask the documentation team to format it and add it to the official documentation. Sorry this slipped through the cracks.

Re: RethinkDB 2.1 is out: high availability

#5

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…

Awesome work guys. Could you give some details on what you're most proud of and what was most challenging?

Re: RethinkDB 2.1 is out: high availability

#6

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…

A bit off-topic, but can you recommend any RethinkDB SaaS providers?

Re: RethinkDB 2.1 is out: high availability

#8
post #5

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…

Awesome work guys. Could you give some details on what you're most proud of and what was most challenging?

Are you interviewing the RethinkDB team here, Russell? ;)

Re: RethinkDB 2.1 is out: high availability

#9
post #6

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…

A bit off-topic, but can you recommend any RethinkDB SaaS providers?

Many of our users use compose.io, and it's pretty solid. I highly recommend them.

Re: RethinkDB 2.1 is out: high availability

#10
post #7

Uhhh what? "Added support for Jepsen tests" shouldn't mean "we sent Kyle a pull request" That seems like deceptive marketing to me. Once the pull request is merged , then you can make that claim. Here's the open PR for Jepsen: https://github.com/aphyr/jepsen/pull/70

I wrote that paragraph of the blog post, and I think I didn't phrase it correctly. What I meant to say is that we hacked Jepsen tests to support RethinkDB, and then ran the tests internally for months. I added that note late last night, definitely could have phrased it better.

We've been working with Kyle on this though, and I think he seemed happy to merge the PR (but he's pretty busy). Hopefully will happen soon, sorry for confusion.

EDIT: here is some context -- https://github.com/rethinkdb/rethinkdb/issues/1493#issuecomm....

Post reply on HN