[MAGNOLIA-2697] Allow for installation on partially clustered instances Created: 23/Apr/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core, updatemechanism
Affects Version/s: 4.0.1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Jan Haderka Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: clustering, configuration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1683 mgnl-files are not extracted on subse... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

When creating partially clustered Magnolia instances, installation is cumbersome. In case of clustering "config" workspace only, other then first installed cluser node will assume installation was already done and will therefore not bootstrap content to other workspaces and not extract templates and other files to local FS either. In case of clustering any other workspace, installation will fail as soon as other then first installed node tries to install/bootstrap content into such workspaces (which was already filled while installing first cluster node) since it assumes installation was not yet performed.
We need to think of mechanism how to configure the clustered instances or to make it easy to discover clustered workspaces and act during installation as appropriate.
Current workaround is to in first case replicate necessary content for other workspaces and for FS manually and in second case to remove any offending bootstrap files from the module on other then fist cluster node prior to installing such a node.



 Comments   
Comment by Magnolia International [ 23/Apr/09 ]
  • the config workspace should only contain configuration and not "runtime" or "installation" information (such as which files were extracted, the current version of each module and so on) – there are or should be other issue reports for this
  • do we want to support arbitrary partial clustering ?
Comment by Philipp Bärfuss [ 24/Apr/09 ]

Partial clustering is crucial in my opinion at least to share date between author an public instance(s). Candidates are:

  • public users (or users in general)
  • comments or any other user generated content you like to see/maintain in the author environment

Actually there are two 'similar' issues.

A) none clustered config triggers twice an installation

  • this is what is described in the issue

B) clustered config does not trigger installation

  • the mgnl-files are not extracted to the second instance: MAGNOLIA-1683

In general I think we cannot solve this for every scenario but for some of the modules we might have some effort to do to make them cluster-able. Actually those we think will be used in this kind of scenarios.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:39:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.