Clustering in eZ Publish Platform refers to setting up your inst= all so you have several web servers running eZ Publish Platform.
Intro: Server setup overvie= w
Diagram illustrates how clustering of eZ Publish Platform is typically s= etup, the parts illustrates the different roles needed for a successful clu= ster setup. Number of web server, memcached servers, Solr server, Varnish s= ervers, Database Severs, NFS servers and if some servers takes care about s= everal roles (typically running memcached across the web server) i= s up to you and your performance needs.
The minimal requirements are the following (with what is currently supported in parentheses):
- Shared HTTP cache (using Varni= sh)
- Shared Persistence cache and Sessions (using Memcached)
- Shared Database (using MySQL/M= ariaDB)
- Shared Filesystem (using NFS)<= /span>
For further details on requirements, see Requirements doc.
While this is not a complete list, further recommendations includes:
- Using a CDN for improved performance and faster ping time worldwide
- Using Solr for better search and better search performance AS OF 5.3 OPTIONALLY USIN= G SOLR (4.X) CLOUD
- Using Active/Passive Database for failover MYSQL/MARIADB CLUSTERING UNDER CONSIDERATI= ON FOR 6.X
- In General: Make sure to use later versions of PHP and MySQL/MariaDB wi= thin what is supported for your e= Z Publish Platform version to get more performance out of each server.
Steps to setup Cluster
To setup Cluster you'll need to:
- Setup DFS Cluster which moves binary files and some legacy cache files to NFS
- Configure Pers= istence Cache to use Memcached
- Setup Varnish, disable Symfo= ny HTTP Cache and setup cache invalidation to purge Varnish cache
- Configure sessions to use cluster = safe Sessions handling