Thanks Pavel. Look forward to have it fixed
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Eugene,
I've reproduced your problem and filed a ticket for that:
https://issues.apache.org/jira/browse/IGNITE-9562
As a temporary workaround, I can suggest you delete persistence data
(cache.dat and partition files) related to that cache in starting node work
directory or don't destroy caches
Hi Pavel
I've prepared the logs you requested. Please download it from this link
https://cloud.mail.ru/public/A9wK/bKGEXK397
hope this will help
regards,
Evgeny
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello Evgeny,
Could you please attach full logs from both nodes in your case #2? Make
sure, that quiet mode is disabled (-DIGNITE_QUIET=false) to have full info
logs.
пт, 7 сент. 2018 г. в 17:41, es70 :
> I have a cluster of 2 ignite (version 2.6) nodes with enabled persistence
> (at
> the time
I have a cluster of 2 ignite (version 2.6) nodes with enabled persistence (at
the time of writing running on my windows machine for test puposes) and
third node (not in the cluster) which I use to run my app in the thick
client mode. The app creates a cache (CacheMode.REPLICATED,
CacheAtomicityMod
I have a cluster of 2 ignite (version 2.6) nodes with enabled persistence (at
the time of writing running on my windows machine for test puposes) and
third node (not in the cluster) which I use to run my app in the thick
client mode. The app creates a cache (CacheMode.REPLICATED,
CacheAtomicityMod
