From 3c23e5978f3f3d3213d45cfb039ddbd793d3b134 Mon Sep 17 00:00:00 2001
From: DMRobertson
The cache factors (i.e. caches.global_factor
and caches.per_cache_factors
) may be reloaded at any time by sending a
+SIGHUP
signal to Synapse using e.g.
kill -HUP [PID_OF_SYNAPSE_PROCESS]
+
+If you are running multiple workers, you must individually update the worker +config file and send this signal to each worker process.
+If you're using the example systemd service
+file in Synapse's contrib
directory, you can send a SIGHUP
signal by using
+systemctl reload matrix-synapse
.
Config options related to database settings.
diff --git a/develop/usage/configuration/homeserver_sample_config.html b/develop/usage/configuration/homeserver_sample_config.html index ec9c6791ec..fe8852586e 100644 --- a/develop/usage/configuration/homeserver_sample_config.html +++ b/develop/usage/configuration/homeserver_sample_config.html @@ -886,6 +886,12 @@ retention: # A cache 'factor' is a multiplier that can be applied to each of # Synapse's caches in order to increase or decrease the maximum # number of entries that can be stored. +# +# The configuration for cache factors (caches.global_factor and +# caches.per_cache_factors) can be reloaded while the application is running, +# by sending a SIGHUP signal to the Synapse process. Changes to other parts of +# the caching config will NOT be applied after a SIGHUP is received; a restart +# is necessary. # The number of events to cache in memory. Not affected by # caches.global_factor. -- cgit 1.5.1