LPAR affinity
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
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).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Gateway load-balancer entry point and its integration with the Discovery service. Determine how local LPAR or host information is represented and how fallback is selected; done means local instances are preferred while unavailable or busy local instances still fall back to remote instances, with coverage for the routing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100