LPAR affinity #4429
Description
Is your feature request related to a problem? Please describe.
Currently, the Gateway load-balances requests across all instances registered in the Discovery service. While this algorithm is usually effective, some services prefer requests to be served on the same LPAR (or host) to reduce latency and network overhead.
Describe the solution you'd like
Clients would like to prioritize local instances in the Gateway load balancer. The Gateway should route traffic to local instances first. It should only proceed to remote LPARs/instances when the local instances are unable to process the request (e.g., they are down or busy).