-
-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High Availability and Scaling setup #2975
Comments
Dendrite wasn't able to run in "HA" mode to begin with, as in you couldn't have more than one component of the same type running at the same time. Going to quote @kegsay for the reason behind this change here:
|
if you could deactivated accounts (after registry without capture ...), here is an server with over >1k:
(see #2464) till you do not release v1.0.0 you would not find any huge server .... for an update process in kubernetes (with zero downtime) it would be nice, to have the possibility running two dendrite's at the same time (on the same database) ... |
Upstream dropped the polylith mode in 0.12.0 as announced in earlier releases. This leads to some renaming of files, see e.g. upstream issue 2975[1]. As I've got no OpenRC system or container right now I can't test the modified OpenRC init scripts. In case you have one feedback either way is appreciated - confirmations that it's working, bug reports if it failes or even just suggestions for improvement. As the ebuild didn't build (failed in the install phase) before this fixup there is no revbump necessary. This commit also adds an service file which is based upon upstream's example for their monolith setup (but with paths in /usr instead of opt)[2]. [1] matrix-org/dendrite#2975 [2] https://github.com/matrix-org/dendrite/blob/main/docs/systemd/monolith-example.service Signed-off-by: Nils Freydank <nils.freydank@posteo.de>
Is Dendriten without polylith still possible to scale and high availability setup possible?
Is it possible to run multiple dendrite with connection to same database?
The text was updated successfully, but these errors were encountered: