Noah Levitt 71221dbe54 minimize impact of down server ...

The last approach was not good, timeout of 0.1 seconds was too short. A
bunch of stuff has to happen in the timeout period inside of
rethinkdb.connect(). It doesn't offer a way to set only the socket
timeout. Even a timeout of 0.5 seconds results in a noticeable error
rate.

The new approach is to put a server in the penalty box for 5 minutes
when it errors. While the server is in the penalty box, we don't try to
connect to it, unless all the servers are in the penalty box, in which
case we try the server that errored least recently.

2018-11-02 18:05:18 +00:00

..

__init__.py

make service registry table name configurable

2017-10-10 11:05:32 -07:00

cli.py

bump dev version number after merging pull request

2017-10-03 16:41:10 -07:00

orm.py

fix dumb bug

2018-03-22 16:01:21 -07:00

rethinker.py

minimize impact of down server

2018-11-02 18:05:18 +00:00

services.py

make service registry table name configurable

2017-10-10 11:05:32 -07:00