You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2016/05/22 19:41:12 UTC

[jira] [Updated] (DRILL-1170) YARN support for Drill

     [ https://issues.apache.org/jira/browse/DRILL-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Rogers updated DRILL-1170:
-------------------------------
    Attachment: Drill-on-YARNDesignOverview.pdf

Short three-page, high-level overview of the design of the Drill-on-YARN feature planned for Drill 1.8. Outlines the design approach, user experience and major components.

If you are a YARN user, and want to run Drill under YARN, please give this outline a read to see if the feature will suit your needs. What is missing? What additional features are needed now or in a later release?

> YARN support for Drill
> ----------------------
>
>                 Key: DRILL-1170
>                 URL: https://issues.apache.org/jira/browse/DRILL-1170
>             Project: Apache Drill
>          Issue Type: New Feature
>            Reporter: Neeraja
>            Assignee: Paul Rogers
>             Fix For: Future
>
>         Attachments: Drill-on-YARNDesignOverview.pdf
>
>
> This is a tracking item to make Drill work with YARN.
> Below are few requirements/needs to consider.
> - Drill should run as an YARN based application, side by side with other YARN enabled applications (on same nodes or different nodes). Both memory and CPU resources of Drill should be controlled in this mechanism.
> - As an YARN enabled application, Drill resource consumption should be adaptive to the load on the cluster. For ex: When there is no load on the Drill , Drill should consume no resources on the cluster.  As the load on Drill increases, resources permitting, usage should grow proportionally.
> - Low latency is a key requirement for Apache Drill along with support for multiple users (concurrency in 100s-1000s). This should be supported when run as YARN application as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)