![]() Copy the deployment to other Seafile nodes.Prepare hardware, operating systems, memcached and database. ![]() ![]() There are a few steps to deploy a Seafile cluster: We recommend to use MariaDB Galera Cluster if you need a database cluster. All app servers serve the data equally to the clients.Īll app servers have to connect to the same database or database cluster. The user data has two parts: One in the MySQL database and the other one in the backend storage cluster (S3, Ceph etc.). More details can be found in background server setup.Īll Seafile app servers access the same set of user data. If you need HA for background task server, you can consider using Keepalived to build a hot backup for it. If more than one background servers are running, they may conflict with each others when doing some tasks. Currently only one background task server can be running in the entire cluster. It should usually be run on a dedicated server for better performance. The background server is the workhorse for various background tasks, including full-text indexing, office file preview, virus scanning, LDAP syncing. More details about memcached configuration is available later. Thus, all Seafile app servers have to connect to the same memcached server (cluster). All shared session information is stored in memcached. The load balancer is responsible for detecting failure and re-routing requests.Įven though Seafile app servers work independently, they still have to share some session information. That means each app server can fail independently without affecting other app server instances. They don't know about each other's state. The Seafile app servers work independently. The web server passes requests from the clients to Seafile app server. There are two main components on the Seafile server node: web server (Nginx/Apache) and Seafile app server. The architecture is visualized in the following picture. That means, you can handle more traffic by adding more machines. Backend storage: Distributed storage cluster, e.g.If one instance fails, the load balancer will stop handing traffic to it. Seafile server cluster: a cluster of Seafile server instances.HA can be achieved by deploying multiple load balancer instances. Load balancer tier: Distribute incoming traffic to Seafile servers.The Seafile cluster solution employs a 3-tier architecture: Read the "Load Balancer Setting" section below for details Architecture ¶ Otherwise sometimes folder download on the web UI can't work properly. Update: Since Seafile Pro server 6.0.0, cluster deployment requires "sticky session" settings in the load balancer. The final configuration of the front-end nodesĭeploy Seahub at Non-root domain or on custom port Download/Uncompress Seafile Professional Server
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |