Re: Problems are enabling Ignite Persistence

[Lokesh Sharma]

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, baseline topology is automatically initialized
when you activate the cluster manually.*"  How can this be so?

Following is the output

➜  bin ./control.sh --activate
> Control utility [ver. 2.6.0#20180710-sha1:669feacc]
> 2018 Copyright(C) Apache Software Foundation
> User: lokesh
>
> 
> Cluster activated
> ➜  bin ./control.sh --baseline
> Control utility [ver. 2.6.0#20180710-sha1:669feacc]
> 2018 Copyright(C) Apache Software Foundation
> User: lokesh
>
> 
> Cluster state: active
> Current topology version: 1
> Baseline nodes not found.




On Mon, Oct 1, 2018 at 12:49 PM Mikael  wrote:

> 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 the original cluster are still available.
> Note that it will only work if you keep persistence directory intact
> between runs.
> I'm also not completely sure whether it will work with one node only.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 28 сент. 2018 г. в 17:33, Lokesh Sharma :
>
>> 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.
>>
>>
>> Yes, tried but had no luck.
>>
>> On Fri, Sep 28, 2018 at 7:59 PM Lokesh Sharma 
>> wrote:
>>
>>> 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
 cluster after you bring all nodes up. Just add ignite.active(true); on
 IgniteConfig.java:92
>>>
>>>
>>> After, I added "ignite.active(true)" it is working for me. Although,
>>> when I remove this line on second run of the app, the original problem
>>> persists. Shouldn't the cluster be automatically activated in the second
>>> run as said in the documentation?
>>>
>>>
>>>
>>> On Fri, Sep 28, 2018 at 6:55 PM ilya.kasnacheev <
>>> ilya.kasnach...@gmail.com> wrote:
>>>
 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 nodes up. Just add ignite.active(true); on
 IgniteConfig.java:92

 The error message about activation requirement was clear and I still
 could
 exist app with Ctrl-C. Maybe you have extra problems if you are on some
 unstable commit of master branch.

 Regards,



 --
 Sent from: http://apache-ignite-users.70518.x6.nabble.com/

>>>
>

Re: Problems are enabling Ignite Persistence

[Mikael]

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 the original cluster are still available.
Note that it will only work if you keep persistence directory intact 
between runs.

I'm also not completely sure whether it will work with one node only.

Regards,
--
Ilya Kasnacheev


пт, 28 сент. 2018 г. в 17:33, Lokesh Sharma >:


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.


Yes, tried but had no luck.

On Fri, Sep 28, 2018 at 7:59 PM Lokesh Sharma
mailto:lokeshh.sha...@gmail.com>> wrote:

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
cluster after you bring all nodes up. Just add
ignite.active(true); on
IgniteConfig.java:92

After, I added "ignite.active(true)" it is working for me.
Although, when I remove this line on second run of the app,
the original problem persists. Shouldn't the cluster be
automatically activated in the second run as said in the
documentation?



On Fri, Sep 28, 2018 at 6:55 PM ilya.kasnacheev
mailto:ilya.kasnach...@gmail.com>>
wrote:

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 nodes up. Just add
ignite.active(true); on
IgniteConfig.java:92

The error message about activation requirement was clear
and I still could
exist app with Ctrl-C. Maybe you have extra problems if
you are on some
unstable commit of master branch.

Regards,



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Problems are enabling Ignite Persistence

[Lokesh Sharma]

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
> cluster after you bring all nodes up. Just add ignite.active(true); on
> IgniteConfig.java:92


After, I added "ignite.active(true)" it is working for me. Although, when I
remove this line on second run of the app, the original problem persists.
Shouldn't the cluster be automatically activated in the second run as said
in the documentation?



On Fri, Sep 28, 2018 at 6:55 PM ilya.kasnacheev 
wrote:

> 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 nodes up. Just add ignite.active(true); on
> IgniteConfig.java:92
>
> The error message about activation requirement was clear and I still could
> exist app with Ctrl-C. Maybe you have extra problems if you are on some
> unstable commit of master branch.
>
> Regards,
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Problems are enabling Ignite Persistence

[ilya.kasnacheev]

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 nodes up. Just add ignite.active(true); on
IgniteConfig.java:92

The error message about activation requirement was clear and I still could
exist app with Ctrl-C. Maybe you have extra problems if you are on some
unstable commit of master branch.

Regards,



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Problems are enabling Ignite Persistence

[Lokesh Sharma]

>
> 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 (
https://bitbucket.org/lokesh_blue/bugdemo/src/56fdf18154d08fd0d5330cf36a78c01cadcb8044/src/main/java/com/bluecoin/common/igniteserver/config/IgniteConfig.java#lines-97
)

It works fine when you run it with "mvn clean spring-boot:run".

But when you enable persistent by uncommenting this line (
https://bitbucket.org/lokesh_blue/bugdemo/src/56fdf18154d08fd0d5330cf36a78c01cadcb8044/src/main/java/com/bluecoin/common/igniteserver/config/IgniteConfig.java#lines-66),
it stops working as expected. The function "test" is executed no more on
application startrup and also the application doesn't exit on Ctrl + C.


On Sat, Sep 22, 2018 at 6:48 AM Denis Magda  wrote:

> 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 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

[Denis Magda]

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 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

[akurbanov]

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

[akurbanov]

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: http://apache-ignite-users.70518.x6.nabble.com/