You can configure the affinity function (RendezvousAffinityFunction <https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.html>). If you set the backup filter, you can customise which nodes are considered for use as backups: cacheConfiguration.setBackups(1); cacheConfiguration.setAffinity(new RendezvousAffinityFunction(1024, (n,p) -> { return !p.hostNames().equals(n.hostNames()); })); Having said that, you’re probably best configuring k8s not to put two Ignite server nodes on a single machine.
Regards, Stephen > On 7 Jul 2020, at 10:42, Humphrey <[email protected]> wrote: > > Let say I have 2 kubernetes nodes and I have 4 ignite server nodes. > This will result (if kubernetes have 2 pods running on each node) in the > following: > > *kubernetes_node1:* ignite_node1, ignite_node2 > *kubernetes_node2:* ignite_node3, ignite_node4 > > I specify that my cache backup = 1 > > Is there a way to configure that the backup data of the ignite_node1 goes on > the ignite_node3 or ignite_node4 and NOT on ignite_node2 (same physical > machine/kubernetes node)? Is there any configuration for this (I assume it's > something on runtime, because we don't know where kubernetes will schedule > the pod)? > > Background: > If kubernetes_node1 goes down, then there won't be any data loss. > > Humphrey > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
