[
https://issues.apache.org/jira/browse/DRILL-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993036#comment-15993036
]
Paul Rogers commented on DRILL-1170:
------------------------------------
Our original intent was to contribute DoY to the Apache Drill project. However,
it is ~12K lines of code, which was too much for the project committers to
review. So, we postponed the contribution until we could find someone
sufficiently motivated to do a code review. Of course, the task of the reviewer
should be simpler now; DoY has been in use for about 9+ months so there should
not be too many obvious bugs to find...
That said, if you can act as a first-line code reviewer, I can restart the
submission process so that DoY becomes part of Apache Drill.
> 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,
> Drill-on-YARNUserGuide.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.15#6346)
