this message in context:
http://apache-ignite-users.70518.x6.nabble.com/RESOLVED-Cache-Entries-get-lost-after-multiple-nodes-started-tp10860p10886.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Neeraj,
The latter most likely means that this node was running in server mode. You
should start it as client:
https://apacheignite.readme.io/docs/clients-vs-servers
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-Entries-get-lost-after-multiple
-
> On Fri, 24/2/17, Neeraj Vaidya wrote:
>
> Subject: Re: Cache Entries get lost after multiple nodes started ?
> To: user@ignite.apache.org
> Date: Friday, 24 February, 2017, 2:07 PM
>
> Another thing I noticed is that if I
> stop the node which initially populat
eeraj
On Fri, 24/2/17, Neeraj Vaidya
wrote:
Subject: Re: Cache Entries get lost after multiple nodes
started ?
To: user@ignite.apache.org
Date: Friday, 24 February, 2017, 12:49 PM
I was able to resolve this after I
changed the Key from AffinityUuid to a s
On Fri, 24/2/17, Neeraj Vaidya
wrote:
Subject: Cache Entries get lost after multiple nodes
started ?
To: user@ignite.apache.org
Date: Friday, 24 February, 2017, 12:05 PM
Hi,
I have populated a cache containing a K,V pair of
.
It gets
I was able to resolve this after I changed the Key from AffinityUuid to a
simple Integer which is auto-incremented. How does one explain the behaviour ?
Regards,
Neeraj
On Fri, 24/2/17, Neeraj Vaidya wrote:
Subject: Cache Entries get lost after
Hi,
I have populated a cache containing a K,V pair of .
It gets populated fine when I start a single node which is responsible for
populating the cache. I am able to retrieve all rows using Zeppelin ignite
interpreter or even using web-console.
However, when I start another node using the same c
