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...