Alexander Kukushkin 7f8e95b334 Next run of ha cycle is rescheduled depending on return value of watch ...

Current etcd implementation does not yet support timeout option when
`wait=true`: https://github.com/coreos/etcd/issues/2468

Originaly I've implemented `watch` method for `Etcd` class in a
following manner: if the leader key was updated just because master
needs to update ttl and watch timeout is not yet expired, I was
recalculating timeout and starting `watch` call once again.
Usually after "restart" we were getting urllib3.exceptions.TimeoutError.
The only possible way to recover after such exception - close socket and
establish a new connection. With pure http it's relatively cheap, but
with https and some kind of authorization on etcd side it would became
rather expensive and should be avoided.

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

..

test_api.py

Refactor directory structure in preparation for building pypi-package

2015-09-04 16:06:44 +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

Make zookeeper module compatible with python3

2015-09-14 17:14:39 +02:00

test_ha.py

Refactor directory structure in preparation for building pypi-package

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

test_patroni.py

Next run of ha cycle is rescheduled depending on return value of watch

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

test_postgresql.py

Next run of ha cycle is rescheduled depending on return value of watch

2015-09-16 10:38:34 +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

Merge branches watch-leader-key and package-refactoring

2015-09-05 16:09:28 +02:00

test_zookeeper.py

Next run of ha cycle is rescheduled depending on return value of watch

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