1 person found this helpful
As the documentation says, the caches must be on the service in order for affinity to work across the caches. Why do you want to run the caches on different services?
We are in a refactoring process and originally those caches had to be in distinct services for proper event processing (avoiding re-entrant calls / poll exception). After reviewing data model and due to new data flow through HotCache, those caches should now be under same service.
Since we have to drop the running service and its caches content to enable data affinity (rolling update is not allowed with a senior member running with default/different data affinity policy), we will also migrate all caches under same service in the process.
I will close this thread, tks for input.