[MAGNOLIA-3971] Cluster ID is not resolved properly Created: 20/Feb/12  Updated: 19/Dec/16

Status: Open
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Ondrej Chytil Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

When cluster ID is specified only in repository configuration file then this value is not set for magnolia.clusterid property which has to be added manually into magnolia.properties file.

Second issue comes with startup in case that instances are running under single JVM. Then startup procedure will log just one cluster id (if configured) for all instances (even when are not clustered). It's caused by treating magnolia.clusterid as native System property - should be done by info.magnolia.cms.core.SystemProperty.


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