Hi,
It seems be all of them resolved. Can I go head and download nightly build
and use it.
Or will it have any impact.
Thanks & Regards,
Venkat
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Great, thanks Denis. I had no idea the thin client existed. This should be
exactly what we need.
From: Denis Mekhanikov
Sent: Friday, August 3, 2018 7:31 PM
To: user@ignite.apache.org
Subject: Re: Cache updates to nodes in client mode
Gordon,
Client nodes are not developed to be used on user
You're using the Multicast IP finder, therefore nodes discover each other via
multicast even if port ranges do not intersect. Try switching to static IP
finder:
https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder
-Val
--
Sent from:
Hello Slava,
Unfortunately demo does not work for me: IComputeJob.Cancel is never called.
In my case an execution of job may take few minutes and I want to receive an
notification about cancellation.
Please check the following code, SimpleJob will never finish, because
IComputeJob.Cancel is
last question is-> in replicated mode all nodes are primary node?
monstereo wrote
> Especially chapter 4 Architecture deep dive
>
> Now:
> 1) primary node is the node where we do igniteCache.put(2)="any string". I
> mean node which we put data in to cache is primary node?
>
> 2) let's say we
many thanks
for last question, I have tried on my laptops and found what I need.
srecon wrote
> Hi,
> Let’s start at the beginning. There is no primary node in Ignite. When we
> say primary node (I will correct the term in the book soon), we mean the
> node that contains the master
We have a requirement where Changes to data from Multiple DBs need to be
periodically & automatically Pushed (not sure how) into various Ignite
Caches
Once the Data is available in the Ignite Caches, it will be persisted
using Ignite Native Persistence, so that in the event of a crash, the Data
I don't want node2 to connect node1. But it is always connectting.
Here is the node1 xml
127.0.0.1:48500..48520
Hi all,
Trying to get an Ignite cluster up and going for testing before taking it
to production.
I've set up Ignite 2.6 on a cluster with a single node on a Google Cloud
Compute instance and I have the web console working as well.
I've imported a table from MySQL and re-run the cluster with the
