Share one origin across several pools
Problem
Interactive, batch, and partner traffic hit the same origin. Separate pool concurrency limits drift. You need one origin concurrency limit, pinned reservations for fairness, and unreserved slots that follow load.
Fix
- Open Capacity and create a budget for the shared concurrency limit.
- Set the shared concurrency limit to the most the upstream can take in flight across every caller.
- Attach the pools that share that origin. Give each a reserved floor (for example interactive 4, batch 2 on a concurrency limit of 10).
- Choose Auto balancing (Business). Fixed caps each pool at its allocation. Auto keeps each pin local and moves float toward load.
- Watch the budget show page: float free and borrowed update as load shifts. The sum of in-flight work across members cannot exceed the shared concurrency limit.
Example on a concurrency limit of 10 with interactive reserved 4 and batch reserved 2:
- Float free starts at 4.
- When batch runs hot, it can borrow up to four float slots, subject to its member Max.
- Interactive always keeps its four pinned slots.
When Fixed is enough
Stay on Fixed when every pool needs a predictable pinned cap and you do not want slots to move. You still get one place to edit the shared concurrency limit and allocations.