Re: Problems are enabling Ignite Persistence

I activated the cluster using "./control.sh --activate" and it successfully activated the cluster. But when I try to see the baseline it says "no nodes found". The docs says "*As explained above,

Re: Problems are enabling Ignite Persistence

Yes it works fine with just one node, I do it all the time for testing. Mikael Den 2018-10-01 kl. 09:06, skrev Ilya Kasnacheev: Hello! Due to https://apacheignite.readme.io/docs/baseline-topology your cluster should indeed auto-activate on a second run provided that all nodes which were in

Re: Problems are enabling Ignite Persistence

Hi Thanks for looking into this. > First, I had to change h2 version dependency from 1.4.197 to 1.4.195 - > maybe > this is because I have later snapshot of Apache Ignite compiled. The version is already 1.4.195. Second, I had to activate the cluster! You have to activate persistent >

Re: Problems are enabling Ignite Persistence

Hello! Seems to be working for me after two changes. First, I had to change h2 version dependency from 1.4.197 to 1.4.195 - maybe this is because I have later snapshot of Apache Ignite compiled. Second, I had to activate the cluster! You have to activate persistent cluster after you bring all

Re: Problems are enabling Ignite Persistence

> > Could you try to send minimalistic reproducer that > shows issue on clean setup? I have reproduced a minimal project that shows this behaviour. Here it is https://bitbucket.org/lokesh_blue/bugdemo/src/master/ It's a simple application. It should execute function "test" when ran. See (

Re: Problems are enabling Ignite Persistence

As a general recommendation, whenever you see a hang like that make a thread dump to see why the threads are blocked. -- Denis On Wed, Sep 19, 2018 at 12:59 PM akurbanov wrote: > Hello, > > Could you also set correct path for IGNITE_HOME or set work directory in > Ignite configuration to

Re: Problems are enabling Ignite Persistence

Hello, Could you also set correct path for IGNITE_HOME or set work directory in Ignite configuration to exclude chances for your /tmp directory to be wiped. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Problems are enabling Ignite Persistence

Hello, There are no issues with starting nodes with enabled persistence, your DataStorageConfiguration is fine, are there any other preconditions to be met to face same issue? Could you try to send minimalistic reproducer that shows issue on clean setup? Regards, -- Sent from:

Problems are enabling Ignite Persistence

geConfiguration(storageCfgPersistence); > > I am facing 2 problems after enabling Ignite persistence: 1 The applications boots up fine with no error but its stuck at that point. It doesn't perform any action that its supposed to perform. I know this because as soon the Ignite completes