Hi Amit, > if the backup count is let's say 2, Ignite won't create a second backup as there are not enough zones Not correct - Ignite will create backups anyway. - A backup is a copy of a partition on another node - With 2 backups every partition will have 3 copies (1 primary, 2 backup), all on different nodes (since you have 10 nodes) - Use ClusterNodeAttributeAffinityBackupFilter to ensure that at least one of the copies is in a different AZ
And that is enough for 3 copies. On Thu, Sep 19, 2024 at 12:10 AM Amit Jolly <amit.jo...@gmail.com> wrote: > 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 >
