This question is a design question. What kids of fault states do you expect to tolerate? What is your failure budget?
Why are you trying to make more than 2 copies of the data distribute across only two failure domains? Also "fail fast" means discover your implementation defects faster than your release cycle, not how fast you can cause data loss. On Tue, Nov 1, 2022, 09:01 Surinder Mehra <[email protected]> wrote: > gentle reminder. > One additional question: We have observed that if available AZs are less > than backups count, ignite skips creating backups. Is this correct > understanding? If yes, how can we fail fast if backups can not be placed > due to AZ limitation? > > On Mon, Oct 31, 2022 at 6:30 PM Surinder Mehra <[email protected]> wrote: > >> Hi, >> As per link attached, to ensure primary and backup partitions are not >> stored on same node, We used AWS AZ as backup filter and now I can see if I >> start two ignite nodes on the same machine, primary partitions are evenly >> distributed but backups are always zero which is expected. >> >> >> https://www.gridgain.com/docs/latest/installation-guide/aws/multiple-availability-zone-aws >> >> My question is what would happen if AZ-1 has 2 machines and AZ-2 has 1 >> machine and ignite cluster has only 3 nodes, each machine having one ignite >> node. >> >> Node1[AZ1] - keys 1-100 >> Node2[AZ1] - keys 101-200 >> Node3[AZ2] - keys 201 -300 >> >> In the above scenario, if the backup count is 2, how would back up >> partitions be distributed. >> >> 1. Would it mean node3 will have 2 backup copies of primary partitions of >> node 1 and 2 ? >> 2. If we have a 4 node cluster with 2 nodes in each AZ, would backup >> copies also be placed on different nodes(In other words, does the backup >> filter also apply to how backup copies are placed on nodes) ? >> >> >>
