[DOCU-120] Clustering tutorial Created: 08/Feb/11  Updated: 30/Sep/19  Resolved: 30/Sep/19

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Done Votes: 0
Labels: outdated, tutorial
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon DOCU-526 Improve documentation regarding clust... Closed
duplicate
is duplicated by DOCU-397 How can i build up an repository for ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: Pre-2019 mgnl-staff requests

 Description   

Write a tutorial for setting up a cluster.

  1. Define a cluster. What problems does it solve?
  2. Make the case for enterprise scalability, advantages for clustering
  3. Explain the difference between a Magnolia cluster and a Jackrabbit cluster.
    • Magnolia cluster. Instances and subscribers. Load balancing. See Performance and availability Tech Brief
    • Jackrabbit cluster. Typical use case is shared storage for a single workspace such as forum to share user generated content such as page comments across cluster nodes. See Clustering in Technical Guide and Richard's comment in this thread. You can also set up a full cluster (all workspaces) and get the cluster benefits.
  4. Write steps for setting up clustered storage for the forum workspace. Provide sample configuration files for download. Search support tickets in Jira and ask Zdenek/Jan to provide configuration files.

Resources:



 Comments   
Comment by Antti Hietala [ 08/Feb/11 ]

When clustering all workspaces:

  • All cluster nodes should be upgraded at the same time, while they are shut down.
  • Activation should happen to only one cluster node. All other nodes will access the same repository.
  • Scheduled jobs should run on one cluster node only.
Comment by Zdenek Skodik [ 09/Feb/11 ]

Yes, I can send you configs for both use cases: whole repository as well as workspace (the commenting one) clustering.

Comment by Philipp Bärfuss [ 12/May/11 ]

make sure we take this two improvements into account:

Comment by Philipp Bärfuss [ 05/Aug/11 ]

I created a brief how-to page in the wiki.
--> http://wiki.magnolia-cms.com/display/WIKI/Setting+up+a+Jackrabbit+Clustering

Comment by Antti Hietala [ 02/May/12 ]

Nice summary of clustering by Richard in the Magnolia Clustering forum thread:

You cannot/should not cluster the "normal" magnolia repository. In particular, I think clustering the workspaces "config", "mgnlVersion" and "mgnlSystem" will cause no end of problems. Instead, what you need to do is create a second jackrabbit repository for your cluster. You can then configure which workspaces will be clustered and which will not by assigning them to either the clustered or the unclustered repository.

Comment by Antti Hietala [ 05/Sep/13 ]

Step by step Magnolia CMS clustering. Blog post by Samuel Schmitt. http://www.samuelschmitt.net/2013/09/step-by-step-magnolia-cms-clustering/

Comment by Jan Haderka [ 09/Apr/14 ]

My biggest pain at the moment is that we explain high av, and load bal clusters, but then we show schema of cluster for sharing data which is none of te cases above. All 3 should be described and each should havei mage. Also we have number of blog and wiki posts how to configure full or partial cluster, we should link them from the page. And lastly we should also mention or show config for tomcat clustering since this is most often what you need too when u start using clusters for high av or load bal.

... Sry for typos ... Ipad only

Comment by Christoph Meier [ 02/Dec/16 ]

ahietala, since you were asking to bump up this ticket on the backlog ...
... forum was mentioned as a use case for a cluster. However, forum is on the way dying out, only used for the commenting module which i also expect to be replaced sooner or later by something more handy (e.g. the webservice written by Jan).
Is there another sue case which you are aware of?

And i think it is a rather sophisticated topic ... but well, let's see

Comment by Julie Legendre [ 30/Sep/19 ]

In order to better focus our efforts on DOCU tickets that are still relevant and important, all tickets older than 18 months have been labelled as outdated and are being automatically closed.
If you think your ticket is still relevant and should remain open, please add a comment and set it back to open.

Generated at Mon Feb 12 01:06:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.