This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Shard master process. #6677
Labels
A-Workers
Problems related to running Synapse in Worker Mode (or replication)
Comments
If there are steps in this direction please also consider not only performance, but high availability. So a single master process would not be ideal in my eyes. See also this issue i opened with focus on ha: #7076 |
@djschilling The point of this project is to run more than one master process. That said, ensuring the whole thing doesn't fall over if 2/3 aren't running would be great. |
Closed
Synapse now supports moving writing of events to a different process. I've opened #7593 to track further work. |
richvdh
added
the
A-Workers
Problems related to running Synapse in Worker Mode (or replication)
label
Feb 16, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently we have a single master process which can quickly become a bottleneck, so we want to be able to run multiple "master" nodes and scale horizontally.
Some notes:
Potential approaches:
The text was updated successfully, but these errors were encountered: