Primary node is calculated for a particular key, this is done by affinity function. This function is stateless and does not depend on weather value exists in cache or not, so the request will always go to the primary node for requested key. In case you have near cache, and value for requested key is already there, there will be no network trip.
However, what you provided is not a description of use case. You previously mentioned that you have 99% misses which makes near cache useless, so I'm wondering why you're trying to use it in the first place. Most likely there is a better approach for you, but I'm having hard time understanding your goals. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Client-near-cache-with-Apache-Flink-tp11627p11850.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
