Or JVM3 and JVM4 would be your Ignite cluster (server nodes) and JMV1 and JVM2 would be client nodes, possibly with near caches.
> On 9 Mar 2020, at 23:04, Evgenii Zhuravlev <e.zhuravlev...@gmail.com> wrote: > > Hi, > > You can use NodeFilter for caches. Please use this JavaDoc for information: > https://www.javadoc.io/doc/org.apache.ignite/ignite-core/latest/org/apache/ignite/util/AttributeNodeFilter.html > > <https://www.javadoc.io/doc/org.apache.ignite/ignite-core/latest/org/apache/ignite/util/AttributeNodeFilter.html> > > Example can be found here: > https://github.com/ezhuravl/ignite-code-examples/blob/master/src/main/java/examples/nodefilter/cache/CacheNodeFilterExample.java > > <https://github.com/ezhuravl/ignite-code-examples/blob/master/src/main/java/examples/nodefilter/cache/CacheNodeFilterExample.java> > > Evgenii > > пт, 6 мар. 2020 г. в 18:34, Edward Chen <java...@gmail.com > <mailto:java...@gmail.com>>: > Hello, > > I want to achieve this topology, do you know how to configure ? > > The critical parts are, cache2 in JVM2 should not be replicated or copied to > JVM 1 . cache1 in JVM1 should not be replicated or copied to JVM 2 . JVM3 > and JVM 4 are each other failed-over backup. > > <laiddfgkccigilen.png> > > Thanks. Ed >
