I would like to know a little bit more about how colocation works. Documentation in this area does not seem to be detailed at least does not seems so clear to me.
Lets say I have 3 server nodes and 3 partitioned regions(Customer, Orders, Shipments) with total buckets=13 and I would like to define that customers are coolocated by domestic and global.
Considering that both groups are big, is that mean that all domestic will go to one bucket and all global to another bucket and rest will be empty (or collocation will relate to servers and then one of the server will be empty(lets assume that there is no copies))?
If that is true I will understand that it is better to define colocation routing object rather granular? Or Gemfire is rather smart enough to still divide data to different buckets and different servers and just try to don't put global and domestic in the same bucket?
Another question if I do colocation does that mean that all keys have to be the same? Do I have to use PartitionResolver key or String is enough?
What Im looking for is to Gemfire try to keep Customers grouped by (Domestic or Global) within region using PartitionResolver and getRoutingObject as Domestic or Global, but I don't want it to just use one bucket for it, I would like them to still be spread and just to minimize number of buckets used.... and then if previous is possible have Orders and Shipments colocated with them by CustomerId not by Domestic or Global (different PartitionResolver)
I'm afraid that exact scenario is not possible, but at least I want to understand how grouping (through PartitionResolver) and colocation works - is it a hard constraint that all related data has to be in one bucket.
And if my fallback scenario is possible which is just colocation by CustomerId using just key and not using PartitionResolver....
Thanks and I will appreciate any input
Jack