Infinispan Cache Container Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 33: Line 33:
:If the <transport> subelement attribute "cluster" is not defined, the cache container name will be used as the value of the JGroups group name, and that means each cache container will create ''its own'' JGroups channel instances, group, etc. They will share configuration, though. Ultimately, each cache container will maintain its own cluster, with a different coordinator, view, etc. It is possible, and quite probable, that different members of the cluster will be coordinators for different cache containers, and that complicates JGroups problems troubleshooting. <br>
:If the <transport> subelement attribute "cluster" is not defined, the cache container name will be used as the value of the JGroups group name, and that means each cache container will create ''its own'' JGroups channel instances, group, etc. They will share configuration, though. Ultimately, each cache container will maintain its own cluster, with a different coordinator, view, etc. It is possible, and quite probable, that different members of the cluster will be coordinators for different cache containers, and that complicates JGroups problems troubleshooting. <br>
</blockquote>
</blockquote>


==default-cache==
==default-cache==


==statistics==
==statistics==
==aliases==
A comma-separated list of aliases. Each alias must be unique among other aliases within the subsystem. They result in alias services being also made available ("service jboss.infinispan.ha-partition").
<font color=red>What is an alias and what is it useful for?</font>

Revision as of 16:09, 31 May 2016

Internal

Overview

As described in the Cache Container section of the Infinispan Concepts page, the <cache-container> element contains global configuration for a set of caches. The cache container global configuration defines global settings shared among all cache instances created for the respective cache container. Shared resources like thread pools, serialization/marshaling settings, transport and network settings are all part of global configuration.

        
<subsystem xmlns="urn:infinispan:server:core:6.4" default-cache-container="clustered">
    <cache-container name="clustered" default-cache="default" statistics="true">
        <transport executor="infinispan-transport" lock-timeout="60000"/>
        <distributed-cache name="default" ... />
        <replicated-cache .../>
    </cache-container>
     ... 
</subsystem>

infinispan Subsystem Configuration

default-cache-container

The name of the cache container to use if no specific name is used.

cache-container Configuration

name

The cache container name. Must be unique among other cache container names.

If the <transport> subelement attribute "cluster" is not defined, the cache container name will be used as the value of the JGroups group name, and that means each cache container will create its own JGroups channel instances, group, etc. They will share configuration, though. Ultimately, each cache container will maintain its own cluster, with a different coordinator, view, etc. It is possible, and quite probable, that different members of the cluster will be coordinators for different cache containers, and that complicates JGroups problems troubleshooting.


default-cache

statistics

aliases

A comma-separated list of aliases. Each alias must be unique among other aliases within the subsystem. They result in alias services being also made available ("service jboss.infinispan.ha-partition").

What is an alias and what is it useful for?