Allow routing broker queries to corresponding broker tenant
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 189
Description
So far, the broker will return BrokerResourceMissingError exception if the querying broker doesn't contain the table, but the tenant contains it. This causes a lot of confusion for users deploying pinot with helmChart, as the service/loadbalancer is exposing all the brokers as one service entrypoint.
The proposed solution is to add the routing mechanism for Brokers to delegate queries to the broker serving the right tenant.
So that we can still keep pinot broker multi-tenant as needed meanwhile, users can also see the pinot broker as a whole service to answer the queries.
Contributor guide
Research direction
Start by reviewing the issue's description and the linked pull request #8813, which is closed and may show the prior direction. Trace how broker queries behave when the requested table exists only in a tenant's broker. Done means queries exposed through the combined broker service reach the broker serving the relevant tenant without breaking broker multi-tenancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100