matrix-docker-ansible-deploy/roles/matrix-synapse/templates/synapse/systemd/matrix-synapse-worker@.serv...

#jinja2: lstrip_blocks: "True"
# Instantiable worker service, running inside the synapse container
# alongside the homeserver main process.
# c.f. https://github.com/matrix-org/synapse/pull/4662
[Unit]
Description=Matrix worker synapse.app.%i
AssertPathExists={{ matrix_synapse_config_dir_path }}/worker.%i.yaml
After=matrix-synapse.service
BindsTo=matrix-synapse.service

[Service]
Type=simple

# Intentional delay, so that the homeserver can manage to start.
ExecStartPre={{ matrix_host_command_sleep }} 5

# no sane way of instancing more than one variable (systemd "cant-fix" 🤦)
# c.f. https://github.com/systemd/systemd/issues/14895#issuecomment-594123923
# So use good ol' shell parameter expansion to get the worker type..
ExecStart=/bin/sh -c "WORKER=%i; WORKER=$${WORKER%%:*}; \
			exec {{ matrix_host_command_docker }} exec \
			--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
			matrix-synapse \
			python -m synapse.app.$${WORKER} -c /data/homeserver.yaml -c /data/worker.%i.yaml"

# wait for worker startup & write out PID of actual worker process so systemd can handle it
ExecStartPost={{ matrix_host_command_sleep }} 5
ExecStartPost={{ matrix_local_bin_path }}/matrix-synapse-worker-write-pid %i /run/matrix-synapse-worker.%i.pid

ExecReload=/bin/kill -HUP $MAINPID
ExecStop=/bin/kill $MAINPID
PIDFile=/run/matrix-synapse-worker.%i.pid
KillMode=process
Restart=always
RestartSec=10
SyslogIdentifier=matrix-synapse-%i

[Install]
WantedBy=matrix-synapse.service
-												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

											
										
										
											5 years ago
+								#jinja2: lstrip_blocks: "True"
-												Improve synapse-workers systemd service template

Is the PID magic gonna work? or will it need an ExecStartPost hack..

											
										
										
											4 years ago
+								# Instantiable worker service, running inside the synapse container
 								# alongside the homeserver main process.
-												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

											
										
										
											5 years ago
+								# c.f. https://github.com/matrix-org/synapse/pull/4662
 								[Unit]
-												synapse workers: supply systemd with actual worker PIDs (requires jq)

also, worker.yaml.j2:
  - hone worker_name
  - remove worker_pid_file entry (would only be used if worker_daemonize
    set to true; also, synapse only knows about the container namespace
    and thus can not provide the required host-view PID)

											
										
										
											4 years ago
+								Description=Matrix worker synapse.app.%i
 								AssertPathExists={{ matrix_synapse_config_dir_path }}/worker.%i.yaml
-												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

											
										
										
											5 years ago
+								After=matrix-synapse.service
 								BindsTo=matrix-synapse.service
 								[Service]
 								Type=simple
-												synapse workers: polishing, cleansing and installation of jq dependency

											
										
										
											4 years ago
+								# Intentional delay, so that the homeserver can manage to start.
 								ExecStartPre={{ matrix_host_command_sleep }} 5
-												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

											
										
										
											5 years ago
-												Improve synapse-workers systemd service template

Is the PID magic gonna work? or will it need an ExecStartPost hack..

											
										
										
											4 years ago
+								# no sane way of instancing more than one variable (systemd "cant-fix" 🤦)
 								# c.f. https://github.com/systemd/systemd/issues/14895#issuecomment-594123923
 								# So use good ol' shell parameter expansion to get the worker type..
-												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

											
										
										
											5 years ago
+								ExecStart=/bin/sh -c "WORKER=%i; WORKER=$${WORKER%%:*}; \
-												synapse workers: polishing, cleansing and installation of jq dependency

											
										
										
											4 years ago
+											exec {{ matrix_host_command_docker }} exec \
-												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

											
										
										
											5 years ago
+											--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
 											matrix-synapse \
 											python -m synapse.app.$${WORKER} -c /data/homeserver.yaml -c /data/worker.%i.yaml"
-												synapse workers: supply systemd with actual worker PIDs (requires jq)

also, worker.yaml.j2:
  - hone worker_name
  - remove worker_pid_file entry (would only be used if worker_daemonize
    set to true; also, synapse only knows about the container namespace
    and thus can not provide the required host-view PID)

											
										
										
											4 years ago
+								# wait for worker startup & write out PID of actual worker process so systemd can handle it
-												synapse workers: polishing, cleansing and installation of jq dependency

											
										
										
											4 years ago
+								ExecStartPost={{ matrix_host_command_sleep }} 5
 								ExecStartPost={{ matrix_local_bin_path }}/matrix-synapse-worker-write-pid %i /run/matrix-synapse-worker.%i.pid
-												synapse workers: supply systemd with actual worker PIDs (requires jq)

also, worker.yaml.j2:
  - hone worker_name
  - remove worker_pid_file entry (would only be used if worker_daemonize
    set to true; also, synapse only knows about the container namespace
    and thus can not provide the required host-view PID)

											
										
										
											4 years ago
-												Improve synapse-workers systemd service template

Is the PID magic gonna work? or will it need an ExecStartPost hack..

											
										
										
											4 years ago
+								ExecReload=/bin/kill -HUP $MAINPID
-												synapse workers: supply systemd with actual worker PIDs (requires jq)

also, worker.yaml.j2:
  - hone worker_name
  - remove worker_pid_file entry (would only be used if worker_daemonize
    set to true; also, synapse only knows about the container namespace
    and thus can not provide the required host-view PID)

											
										
										
											4 years ago
+								ExecStop=/bin/kill $MAINPID
 								PIDFile=/run/matrix-synapse-worker.%i.pid
-												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

											
										
										
											5 years ago
+								KillMode=process
 								Restart=always
 								RestartSec=10
 								SyslogIdentifier=matrix-synapse-%i
 								[Install]
 								WantedBy=matrix-synapse.service