Your clients don’t “know” about each other, so, yes, they’re going to duplicate work. Could you use the Service Grid to run your client? That way it would fail over automatically.
Regards, Stephen > On 16 Oct 2019, at 16:04, SunSatION <sunsation.xs...@gmail.com> wrote: > > Hi, > > We have a scenario where we're using Ignite Kafka Datastream to write to > cache which are setup using PARTITIONED affinity. We're using continuous > queries to identify changes to each cache entry and perform an action if the > entry changes which are running on the client. We have 3 server nodes and 3 > client nodes for HA. The problem is that all clients are receiving the cache > changes and the action is performed 3 times, once for each client. We are > unable to use the affinity key of the cache entry as it returns the id of > the server nodes. > > Any ideas on the a way that the action is performed once without the client > nodes knowing of each other? > > Thanks, > Dorian > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
