16 Commits (bca30cefee3849813565dd71e571172818629d85)

Author	SHA1	Message	Date
Richard van der Hoff	cc6243b4c0	document the REPLICATE command a bit better (#6305) ... since I found myself wonder how it works	5 years ago
Andrew Morgan	54fef094b3	Remove usage of deprecated logger.warn method from codebase (#6271) ... Replace every instance of `logger.warn` with `logger.warning` as the former is deprecated.	5 years ago
Amber Brown	32e7c9e7f2	Run Black. (#5482)	6 years ago
Richard van der Hoff	f570916a3e	Add parse_row method to replication stream class ... This will allow individual stream classes to override how a row is parsed.	6 years ago
Richard van der Hoff	acaa18f7dd	Fix/improve some docstrings in the replication code. (#4949)	6 years ago
Erik Johnston	6870fc496f	Move connecting logic into ClientReplicationStreamProtocol	6 years ago
Erik Johnston	25814921f1	Increase the max delay between retry attempts ... Otherwise if you have many workers they can easily take out master with their connection attempts	6 years ago
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.	6 years ago
Amber Brown	c4b3698a80	Make the replication logger quieter (#4108)	6 years ago
Richard van der Hoff	0e8d78f6aa	Logcontexts for replication command handlers ... Run the handlers for replication commands as background processes. This should improve the visibility in our metrics, and reduce the number of "running db transaction from sentinel context" warnings. Ideally it means converting the things that fire off deferreds into the night into things that actually return a Deferred when they are done. I've made a bit of a stab at this, but it will probably be leaky.	6 years ago
Richard van der Hoff	f59be4eb0e	Fix unit tests ... on_notifier_poke no longer runs synchonously, so we have to do a different hack to make sure that the replication data has been sent. Let's actually listen for its arrival.	6 years ago
Amber Brown	49af402019	run isort	6 years ago
Amber Brown	07cad26d65	Remove all global reactor imports & pass it around explicitly (#3424)	7 years ago
Erik Johnston	78cefd78d6	Make workers report to master for user ip updates	8 years ago
Erik Johnston	69b3fd485d	Fix incorrect type when using InvalidateCacheCommand	8 years ago
Erik Johnston	52bfa604e1	Add basic replication client handler and factory	8 years ago