Ignite provides various cache configurations that allow you to control the behavior of the cache to suite your application needs. Cache properties are defined in the
CacheConfiguration class that is passed to the cluster via the
IgniteConfiguration.setCacheConfiguration() method. It defines all configuration parameters required to start a cache in the cluster. You can have multiple caches configured with different names within one cluster. An Ignite cache can be configured for the following features:
Partitioning and Replication - Ignite provides three different modes of cache operation:
LOCAL. A cache mode is configured for each cache. Cache modes are defined in
Partition Loss Policies - Allows you to configure how the cache should behave when some of the data partitions get lost due to the failure of primary and backup nodes that held a copy of the partitions.
Primary & Backup Copies - In
PARTITIONED mode, nodes to which the keys are assigned are called primary nodes for those keys. You can also optionally configure any number of backup nodes for cached data.
Cache Groups - You can configure caches within a single cache group. This allows sharing various internal structures which in turn boosts topology events processing and decreases overall memory usage.
Cache Template - Cache templates are useful when you want to create a cache with the same configuration as an existing cache in the cluster. This allows you to create a cache without defining a long list of configuration parameters.
Updated 7 months ago