Hi Team We are planning to run 10 node Ignite clusters in AWS with 5 nodes each into two availability zones. Using Kubernetes topologyspreadconstraints we have made sure that no two Ignite pods are started on the same virtual machine/node/host.
I understand with ClusterNodeAttributeAffinityBackupFilter i can force ignite to store the backup in a different zone if backup count is 1. But if the backup count is let's say 2, Ignite won't create a second backup as there are not enough zones. My question is if i have backup count 2, How can I use ClusterNodeAttributeAffinityBackupFilter or (custom AffinityBackupFilter) to have at least one backup in each zone and another backup anywhere else where available. I think in order to achieve what I am thinking somehow I need currentTopologySnapshot available in ClusterNodeAttributeAffinityBackupFilter or custom AffinityBackupFilter Thanks, Amit Jolly
