4 Commits

Author	SHA1	Message	Date
Slavi Pantaleev	70796703d3	Run Synapse workers in their own containers ... This switches the `docker exec` method of spawning Synapse workers inside the `matrix-synapse` container with dedicated containers for each worker. We also have dedicated systemd services for each worker, so this are now: - more consistent with everything else (we don't use systemd instantiated services anywhere) - we don't need the "parse systemd instance name into worker name + port" part - we don't need to keep track of PIDs manually - we don't need jq (less depenendencies) - workers dying would be restarted by systemd correctly, like any other service - `docker ps` shows each worker separately and we can observe resource usage	2021-01-25 12:14:46 +02:00
Marcel Partap	a4125d5446	synapse workers: polishing, cleansing and installation of jq dependency	2020-10-23 20:49:53 +02:00
Marcel Partap	cf452fdf0a	Fix corner-cases found through testing (aka ansible is nuts)	2020-04-19 19:05:03 +02:00
Marcel Partap	353bc7c362	Add initial support for synapse workers ... · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md	2020-04-19 19:05:03 +02:00