Please do not use term "atomic cache" for system caches that hold internal
data for atomic data structures. This is very confusing.

You are right, currently there is no logic that will validate cache
configuration. It definitely should be fixed. And having configuration
parameters encoded in cache name, like it is currently implemented for
collections, is one of the most straightforward approaches.

On Mon, Apr 9, 2018 at 4:19 PM, akurbanov <> wrote:

> I've attached .java file to
> jira/browse/IGNITE-2096
> Atomic references created with cacheMode=REPLICATED configuration are being
> lost when first references are created with cacheMode=PARTITIONED, no
> validation errors.
> --
> Sent from:

Best regards,

Reply via email to