[
https://issues.apache.org/jira/browse/IGNITE-28993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-28993:
----------------------------------------
Description:
Check :
GridLocalConfigManager#restoreCaches
{code:java}
if (!F.isEmpty(skippedConfigs)) {
U.warn(log, "Static configuration for the following caches
will be ignored because a persistent " +
"cache with the same name already exist (see " +
"https://apacheignite.readme.io/docs/cache-configuration for more information):
" +
skippedConfigs);
}
{code}
just for history, appropriate link contain this text:
{code:java}
Cache Configuration
❗️
This is a legacy Apache Ignite documentation
The new documentation is hosted here: https://ignite.apache.org/docs/latest/
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: PARTITIONED, REPLICATED, and LOCAL. A cache mode is configured for
each cache. Cache modes are defined in CacheMode enumeration.
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.
{code}
was:
Check :
GridLocalConfigManager#restoreCaches
{code:java}
if (!F.isEmpty(skippedConfigs)) {
U.warn(log, "Static configuration for the following caches
will be ignored because a persistent " +
"cache with the same name already exist (see " +
"https://apacheignite.readme.io/docs/cache-configuration for more information):
" +
skippedConfigs);
}
{code}
> Rework waning cause it link to legacy resource: apacheignite.readme.io
> ----------------------------------------------------------------------
>
> Key: IGNITE-28993
> URL: https://issues.apache.org/jira/browse/IGNITE-28993
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.18
> Reporter: Evgeny Stanilovsky
> Priority: Major
>
> Check :
> GridLocalConfigManager#restoreCaches
> {code:java}
> if (!F.isEmpty(skippedConfigs)) {
> U.warn(log, "Static configuration for the following
> caches will be ignored because a persistent " +
> "cache with the same name already exist (see " +
>
> "https://apacheignite.readme.io/docs/cache-configuration for more
> information): " +
> skippedConfigs);
> }
> {code}
> just for history, appropriate link contain this text:
> {code:java}
> Cache Configuration
> ❗️
> This is a legacy Apache Ignite documentation
> The new documentation is hosted here:
> https://ignite.apache.org/docs/latest/
> 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: PARTITIONED, REPLICATED, and LOCAL. A cache mode is configured for
> each cache. Cache modes are defined in CacheMode enumeration.
> 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.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
