3 ms·
I love the way you guys have stated the advantages and disadvantages of RethinkDB in your FAQs. Just wondering about one thing in there: "RethinkDB is a great
by nullspace 14y ago
I love the way you guys have stated the advantages and disadvantages of RethinkDB in your FAQs. Just wondering about one thing in there:
"RethinkDB is a great choice if you .... are planning to run anywhere from a single node to sixteen node clusters."
With a sharded master-slave setup with one slave each, this leaves us with a total of 8 shards. This is enough for most use cases, but is there a reason it is limited to 16 nodes?
- coffeemug 14y agoThere is a bottleneck in the metadata propagation code that slows down the system after roughly 16 nodes (there is one place where we used an O(N^3) algorithm in the interest of shipping the product). This isn't an inherent limitation, just the state of affairs today. We'll resolve this in the next few releases, but we wanted to be up front about this limitation for the time being.
- jdoliner 14y agoShort answer it's a pretty arbitrary cutoff. 16 is the largest number of nodes we've done sufficiently rigorous tests on to be sure that things go smoothly. So that's the highest number we're comfortable citing on our site. It's a conservative estimate though so you should be fine straying past it. We know of a few things which becoming scalability concerns with a large numbers of machines but we're talking close to 100 machines. These will hopefully be addressed soon.