Thanks Dmitry
I started server node via bin/ignite.sh but didn't override DEFAULT_CONFIG
to point on my configuration
As result, client node was using my config and server node used default
config.
Persistence is working after fixing this.
On Tue, Mar 6, 2018 at 11:55 AM, Dmitry Pavlov
Hi Oleksandr,
Could you please check Ignite logs for messages were persistence directory
located?
When Ignite is started from code, it is possible that Ignite is not able to
locate IGNITE_WORK or IGNITE_HOME and creates work files in temp dir. Start
scripts always provide this setting, but in
Hi Team,
I'm trying to configure persistent cache.
Specifically I need to cache key-value pairs and they should be also stored
to persistent storage.
Here is my configuration:
[ignite.xml]
...
