News for hackers. Stuff that matters.
Re:RethinkDB 1.7: hot backup, atomic set/get, 10x insert per... by charlieyuan on Thursday July 04, 2013 @02:58AM (#5989502)
Is there a plan to fix: "If the machine is acting as a master for any shards, the corresponding tables lose read and write availability (out-of-date reads remain possible as long as there are other replicas of the shards). ... Currently, RethinkDB does not automatically declare machines dead after a timeout. This can be done by the user, either in the web UI, manually via the command line, or by scripting the command line tools."

http://www.rethinkdb.com/docs/advanced-faq/#what-happens-whe...

There are no comments on this comment yet.