Alexander Kukushkin 0096b6b06f Schedule update of machines cache when api_execute call has failed ...

Such situation could happen if we replaced all etcd nodes except one
which was used by patroni. After replacing the last node patroni will
try to execute request on all other nodes from machines_cache but non of
them are available. Michines cache would became empty and patroni will
stick to the latest node which was available in the machines_cache and
will never try to refresh machines_cache from dns for example.

Currently machines cache is refreshed only when one request to the etcd
cluster has failed, but probably it should be done periodically, for
example every minute...

2015-10-21 10:56:43 +02:00

..

test_api.py

Improve tests

2015-10-20 14:36:49 +02:00

test_async_executor.py

add missing tests for async_executor

2015-10-09 16:02:34 +02:00

test_aws.py

Refactor directory structure in preparation for building pypi-package

2015-09-04 16:06:44 +02:00

test_etcd.py

Schedule update of machines cache when api_execute call has failed

2015-10-21 10:56:43 +02:00

test_ha.py

Mock etcd client delete method

2015-10-15 09:08:16 +02:00

test_patroni.py

use Event.wait instead of sleep

2015-10-02 10:26:48 +02:00

test_postgresql.py

fix pep8 formatting

2015-10-15 09:08:33 +02:00

test_restore.py

Refactor directory structure in preparation for building pypi-package

2015-09-04 16:06:44 +02:00

test_utils.py

Refactor Postgresql.query method to use common retry mechanism

2015-09-20 13:54:30 +02:00

test_zookeeper.py

bugfix in zookeeper module:

2015-10-08 13:07:38 +02:00