praveenc7 opened a new pull request, #17124:
URL: https://github.com/apache/pinot/pull/17124

   ## Summary
   1. Add support for custom class implementation using reflections to avoid 
creating a custom implementation of the entire starter class. This follows the 
convention we generally use for some class in pinot-minion
   2. Removing WorkloadBudgetExceeded Error code since it is no longer used and 
instead SERVER_RESOURCE_LIMIT_EXCEEDED is generalized to be used instead also 
WorkloadBudgetExceeded conflicts TOO_MANY_REQUESTS error-code leading to issues 
on broker testing side
   3. Fetch workload budgets on startup - Brokers and servers now fetch their 
assigned workload budgets from the controller during initialization, ensuring 
budgets are available immediately after restart
   4. Broker debug API - Added /debug/queryWorkloadCost endpoints to brokers 
(matching existing server APIs) for runtime workload inspection
   5. Use IdealState for broker resolution - Controller now uses IdealState 
instead of ExternalView when propagating workload configs, ensuring offline 
brokers (e.g., during rolling restart) receive updates
   6. canAdmitQuery should check whether enforcement is enabled—similar to how 
WorkloadResourceAggregator does—instead of relying on costCollection. This 
ensures correct behavior in scenarios where cost collection is active but 
enforcement is intentionally disabled for workload analysis or monitoring 
purposes.
   7.  Foundational metrics to track basic availability for workload
   
   
   ## Testing Done
   Unit test and Integ test


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to