Hi Nick, Yes, client node has up to date information regarding affinity and will use it to send request to the proper server node.
If you're comparing client node to thin client then client node has more overhead since it's starting cluster node and processes discovery and communication events in the cluster, due to that it has information regarding affinity. On the other hand, the thin client sends all requests to the same server node and after that the request will be redirected to other nodes if it's necessary. Regards, Igor On Thu, Jul 25, 2019 at 6:37 PM milkywayz <npori...@bandwidth.com> wrote: > Hello, I plan on using an Ignite node topology as follows: > 1) Application configured as an Ignite Client that handles distributing > requests to the correct server node. > 2) 3+ Partitioned Server nodes that handle cache storage and processing of > requests. > 3) Each server node has two caches which use AffinityKey for pinning > entries > in the two caches to one node for a given key. > > Questions: > 1) Will the client have up to date access to the AffinityFunction for the > two caches? > 2) What sort of overhead is associated with running as client mode? I want > to make it as dumb as possible, so it would only just be aware of topology > changes and always have the latest AffinityFunction for the partitioned > server node topology. > > Thank you, Nick. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
