Yuci, As far as I know client node also could start *fully functional* LOCAL cache.
On Tue, Dec 6, 2016 at 10:36 PM, yucigou <[email protected]> wrote: > Hi Andrew, > > I have looked at Local Mode cache. > > But the thing is that Local Mode cache is located on server nodes. > > Suppose I have two server nodes, node A and B, and one client node, node C. > > Node C has a near cache, and server node A and B are of Local Mode cache. > > And then client node C puts an entry in the cache of server node A, and > also > its own near cache. > > After a certain period of time, the entry is evicted from node C's near > cache, while still being kept in node A. > > Now client node C would like to access the entry. Would Ignite always know > that it should go to node A to look for the entry? If Ignite happens to go > to node B, node B would know nothing about the entry, as the cache is set > in > Local Mode. > > (But if Ignite knows exactly that it should go to node A to retrieve that > entry, then that would be perfect!) > > Thank you, > Yuci > > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Is-it-possible-to-create-a-near- > cache-without-any-copy-on-servers-nodes-tp9415p9419.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
