Infinispan Configuration: Difference between revisions
| Line 10: | Line 10: | ||
A JDG instance intended to provide access to an internal local cache (maintained within the memory of the JVM running the JDG instance) is configured from <tt>$JDG_HOME/standalone/configuration/standalone.xml</tt> A JDG instance intended to cluster with other instance to provide a distributed cache space is configured from <tt>$JDG_HOME/standalone/configuration/clustered.xml</tt>. | A JDG instance intended to provide access to an internal local cache (maintained within the memory of the JVM running the JDG instance) is configured from <tt>$JDG_HOME/standalone/configuration/standalone.xml</tt> A JDG instance intended to cluster with other instance to provide a distributed cache space is configured from <tt>$JDG_HOME/standalone/configuration/clustered.xml</tt>. | ||
The clustered instance is supposed to be started using <tt>$JDG_HOME/bin/clustered.sh</tt>. When started this way, the configuration file <tt>$JDG_HOME/bin/clustered.conf</tt> is sourced. However, when systemctl starts the instance, the systemd startup scripts are written to invoke <tt>$JDG_HOME/bin/standalone.sh -c clustered.xml</tt> and this sources <tt>standalone.conf</tt> and not <tt>clustered.conf</tt>. It is best to keep both of those in sync with configuration. | |||
=Procedures= | =Procedures= | ||
Revision as of 18:51, 27 May 2016
Internal
Relevance
- JDG 6.6.0
JDG Configuration Files
A JDG instance intended to provide access to an internal local cache (maintained within the memory of the JVM running the JDG instance) is configured from $JDG_HOME/standalone/configuration/standalone.xml A JDG instance intended to cluster with other instance to provide a distributed cache space is configured from $JDG_HOME/standalone/configuration/clustered.xml.
The clustered instance is supposed to be started using $JDG_HOME/bin/clustered.sh. When started this way, the configuration file $JDG_HOME/bin/clustered.conf is sourced. However, when systemctl starts the instance, the systemd startup scripts are written to invoke $JDG_HOME/bin/standalone.sh -c clustered.xml and this sources standalone.conf and not clustered.conf. It is best to keep both of those in sync with configuration.