Thanks Stephan. I am saying one ignite-node/pod/k8 node spread across availability zones
On Tue, Jul 21, 2020 at 9:51 AM Stephen Darlington < [email protected]> wrote: > 1) I think you’re saying you have two Ignite nodes on one physical > machine. What I mean is, don’t do that. All else being equal, one server > node per physical machine is the way to go > > 2) This is an Ignite feature and not limited to any particular cloud > vendor. It does rely on your cloud vendor “publishing” the underlying > machine (or availability zone) as an environment variable so Ignite can > find it > > On 21 Jul 2020, at 14:01, narges saleh <[email protected]> wrote: > > Hi Stephen, > 1) [Having said that, you’re probably best configuring k8s not to put two > Ignite server nodes on a single machine.] > Do you mean by having k8s place the VMs in different availability zones? > > Then how would you tell ignite to place the backups in a different zone? > I've read this is possible via affinityBackupFilter. Which brings up my > next question. > > 2) Is affinityBackupFilter available with all public cloud platforms or > just AWS? > > thanks. > > On Tue, Jul 7, 2020 at 5:20 AM Stephen Darlington < > [email protected]> wrote: > >> 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/ >> >> >> >> > >
