Hello! 1) When there is an overflow, either page eviction kicks in, or, if it is disabled, you get an IgniteOOM, after which the node is no longer usable. Please avoid overflowing any data regions since there's no graceful handling currently. 2) I don't think so. You can't easily confine half of cache's data to one cluster group and another half to other group.
Such scenarios are not recommended. We expect that all partitions have same amount of data. Not that there are a few gargantuan partitions that don't fit in a single node. Regards, -- Ilya Kasnacheev вт, 20 авг. 2019 г. в 06:29, narges saleh <snarges...@gmail.com>: > Hello All, > > I'd appreciate your answers to my questions. > > 1) Assuming I use affinity key among 4 caches, and they all end up on the > same ignite node. What happens where is an overflow? Does the overflow data > end up on a joined node? How do I keep the related data from all the caches > close to each other when the volume of exceeds a single node? > > 2) Is there a concept of cluster affinity, meaning having a cluster group > defined based on some affinity key? For example, if I have two departments > A and B, can I have a cluster group for department A and another for > department B? > > Thanks, > Narges >
