[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: |
|
||||||||
| 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. |
| Comments |
| Comment by Magnolia International [ 23/Apr/09 ] |
|
| 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:
Actually there are two 'similar' issues. A) none clustered config triggers twice an installation
B) clustered config does not trigger installation
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. |