Erik Johnston 313987187e Fix tightloop over connecting to replication server ... If the client failed to process incoming commands during the initial set up of the replication connection it would immediately disconnect and reconnect, resulting in a tightloop. This can happen, for example, when subscribing to a stream that has a row that is too long in the backlog. The fix here is to not consider the connection successfully set up until the client has succesfully subscribed and caught up with the streams. This ensures that the retry logic timers aren't reset until then, meaning that if an error does happen during start up the client will continue backing off before retrying again.		2019-02-26 15:05:41 +00:00
..
__init__.py	Fix up docs	2017-03-31 11:19:24 +01:00
client.py	Fix tightloop over connecting to replication server	2019-02-26 15:05:41 +00:00
commands.py	Fix tightloop over connecting to replication server	2019-02-26 15:05:41 +00:00
protocol.py	Don't truncate command name in metrics	2018-10-29 17:34:21 +00:00
resource.py	Wrap a number of things that run in the background	2018-07-25 09:41:12 +01:00
streams.py	Fix minor typo in exception	2018-09-13 11:51:12 -06:00