To fix it you can run:
control.sh --cache reset_lost_partitions default-ds-group,default-volatile-ds-group@volatileDsMemPlc
Some system caches are partitioned and can loss the partitions as well as normal user caches.
The command above should help in your case.
As the work around you can change the backup factor and change the group:
https://www.gridgain.com/sdk/latest/javadoc/org/apache/ignite/configuration/AtomicConfiguration.html#setBackups-int-https://www.gridgain.com/sdk/latest/javadoc/org/apache/ignite/configuration/AtomicConfiguration.html#setGroupName-java.lang.String-
If the structure is volatile, it will have the group name "default-volatile-ds-group". Otherwise, if no group name is given, the name will be "default-ds-group". As far as I know it has some cache creation logic based on this.
Try the following example for your data structure:
AtomicConfiguration cfg = new AtomicConfiguration().setGroupName("testgrp"); cfg.setBackups(1); cfg.setCacheMode(CacheMode.PARTITIONED); IgniteAtomicReference<String> ref = ignite.atomicReference("ref", cfg, "d", true);
Regards,Andrei