- Server operating system version
- Ubuntu 22.04
- Plesk version and microupdate number
- Plesk Obsidian 18.0.50
Hi everyone!
Have you already seen a blog post with "proof of concept" on how it is possible to start Plesk on top of high-availability cluster?
The idea of such Plesk HA cluster is based on moving all "single point of failure" resources out of server(s), it based on centralized database and centralized file storage (NFS) features. After that Plesk is only a process (to be honest lots of processes) that works on one of nodes. And Plesk could be quickly started on another cluster node if the the previous cluster node is failed.
Independently of HA cluster, using centralized resources could help to decrease cost of maintenance Plesk and infrastructure if you have lots of Plesk installations. On the same time, splitting "all-in-one" server into a few simple components/servers (Plesk, database, file server) also allows to increase service availability because the service is based on set of more simpler components.
We would love to get any feedback related Plesk HA in this forum thread! What do you think about the "proof of concept". Would you like to use it? What blockers do you see? What should be impovemed first? Feel free to share your thoughts!
Have you already seen a blog post with "proof of concept" on how it is possible to start Plesk on top of high-availability cluster?
The idea of such Plesk HA cluster is based on moving all "single point of failure" resources out of server(s), it based on centralized database and centralized file storage (NFS) features. After that Plesk is only a process (to be honest lots of processes) that works on one of nodes. And Plesk could be quickly started on another cluster node if the the previous cluster node is failed.
- Plesk with Centralized Database and Network File System
- Input - Plesk with Centralized Database
- Input - Plesk with Centralized File Storage (based on NFS)
Independently of HA cluster, using centralized resources could help to decrease cost of maintenance Plesk and infrastructure if you have lots of Plesk installations. On the same time, splitting "all-in-one" server into a few simple components/servers (Plesk, database, file server) also allows to increase service availability because the service is based on set of more simpler components.
We would love to get any feedback related Plesk HA in this forum thread! What do you think about the "proof of concept". Would you like to use it? What blockers do you see? What should be impovemed first? Feel free to share your thoughts!
Last edited: