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
..
http	Fix registration on workers (#4682)	2019-02-20 18:47:31 +11:00
slave	Fix state cache invalidation on workers	2019-02-22 14:38:14 +00:00
tcp	Fix tightloop over connecting to replication server	2019-02-26 15:05:41 +00:00
__init__.py	Add a /replication API for extracting the updates that happened on	2016-03-01 14:49:41 +00:00