Which Karaf configuration files are synchronized between cluster nodes in Jahia?

Question

In Jahia clusters, are all Karaf configuration files automatically synchronized?

Answer

No. Not all configuration files located in digital-factory-data/karaf/etc are synchronized between cluster nodes.
Replication is managed by Apache Karaf Cellar, through the configuration file:

/digital-factory-data/karaf/etc/org.apache.karaf.cellar.groups.cfg

This file defines whitelists and blacklists for each cluster group. These control which bundles, configurations, and features are propagated across the cluster. This filtering is called the blocking policy:

• Inbound = what the node accepts from the cluster
• Outbound = what the node sends to the cluster

Jahia defaults

By default, Jahia excludes several sensitive configurations from synchronization, for example:

• org.apache.karaf.shell (SSH console host/port/keys)
• org.apache.karaf.management (JMX/management)
• org.ops4j.pax.logging (logging)
• org.ops4j.pax.web (HTTP/Whiteboard)

These PIDs are blacklisted inbound and outbound, so their files are not synchronized and must be updated manually on each node.

Other configurations (not blacklisted) are synchronized according to the sync policy defined in the same file, usually cluster (cluster state is authoritative).
 

See the Apache Karaf Cellar documentation – Blocking policy for more details.