[
https://issues.apache.org/jira/browse/DRILL-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hongze Zhang updated DRILL-5299:
--------------------------------
Description: So far we can have 2 query queues that are split based on the
cost model. For serving multiple users and multiple businesses, Drill cluster
maintainers would always like to control the query concurrency that are
allocated for a concrete user or a concrete businesses. Which means, each user
or business can have its own "query pool" defined by a specific "pool size".
(was: So far we can have 2 query queues that are split based on the cost model.
For serving multiple users and multiple businesses, Drill cluster maintainers
always like to control the query concurrency that are allocated for a concrete
user or a concrete businesses. Which means, each user or business can have its
own "query pool" defined by a specific "pool size".)
> Query queues can be split by different users or different businesses
> --------------------------------------------------------------------
>
> Key: DRILL-5299
> URL: https://issues.apache.org/jira/browse/DRILL-5299
> Project: Apache Drill
> Issue Type: Improvement
> Components: Query Planning & Optimization
> Affects Versions: Future
> Environment: RH Linux / OpenJDK 8
> Reporter: Hongze Zhang
>
> So far we can have 2 query queues that are split based on the cost model. For
> serving multiple users and multiple businesses, Drill cluster maintainers
> would always like to control the query concurrency that are allocated for a
> concrete user or a concrete businesses. Which means, each user or business
> can have its own "query pool" defined by a specific "pool size".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
