Internally, there are also some soft capabilities. These include using planner.max.width.per.node and queues:
https://drill.apache.org/docs/configuring-resources-for-a-shared-drillbit/ -- Jacques Nadeau CTO and Co-Founder, Dremio On Tue, Aug 4, 2015 at 6:38 AM, John Omernik <[email protected]> wrote: > I am looking to work with drill in a managed cluster (having it play nice > with Mesos). While I can limit the ram in the drill-env.sh, the CPU is not > limitable, therefore, drill can just grab all the CPU resources it wants. > Is there any plans to include some self limiting to Drill on CPU resources? > In the docs it says use CGroups, which I need to read up on, but frameworks > like Spark and Impala allow you to set the CPU resources in the framework. > Is CGroups going to get me similar behavior to those? Are there > disadvantages to setting these resources in drill itself? > > Thanks > > John >
