System.out.println("finish listener");
return true;
}
};
On Nov 12, 2018 12:31, "Vadym Vasiuk" wrote:
In other words - there is no way to do something with the cache after event
which signals about its creation.
On Mon, Nov 1
In other words - there is no way to do something with the cache after event
which signals about its creation.
On Mon, Nov 12, 2018, 11:57 Ilya Kasnacheev Cross-posting from SO:
>
> As a rule you should not perform cache operations, or most of other
> operations that block or access Ignite
I want to be able to monitor events of cache creation in Apache Ignite.
Whenever such events happen - I want to be able to do something with those
caches, after they are created, but before anyone else could inserts
something.
So I used local listener. Below is all the code:
@Configuration
Hi All,
I have Ignite cluster which consists of two nodes. Each node after start
creates a continuous query which calls atomicLong.incrementAndGet() in
"onUpdated" method:
continuousQuery.setLocalListener(new
CacheEntryUpdatedListener() {
@Override public void
Has anyone some advice for this situation?
Thanks.
On Mon, May 21, 2018, 21:29 Vadym Vasiuk <vvas...@gmail.com> wrote:
> HI All,
>
> I also noticed that if I bounce one of two nodes and data is then
> distributed as I described (one node has all the PRIMARY entries and sec
to make data distribution
normal?
Thanks.
On Mon, May 21, 2018 at 2:49 PM, Vadym Vasiuk <vvas...@gmail.com> wrote:
> Hi Stanislav,
>
> Yes persistence is enabled and version is 2.4.
>
> Have tried to update topology after one node restart with below code from
> clie
Hi Stanislav,
Yes persistence is enabled and version is 2.4.
Have tried to update topology after one node restart with below code from
client:
Collection nodes = ignite.cluster().forServers.nodes();
ignite.cluster().setBaselineTopology(nodes);
And after that I still have all primary entries
