drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-6068) Drill should support user/distribution specific configuration checks during startup
Date Sat, 24 Feb 2018 17:08:00 GMT

    [ https://issues.apache.org/jira/browse/DRILL-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375676#comment-16375676

ASF GitHub Bot commented on DRILL-6068:

Github user amansinha100 commented on the issue:

    @kkhatua since this was combined with #1082 which is merged, you can close this PR. 

> Drill should support user/distribution specific configuration checks during startup
> -----------------------------------------------------------------------------------
>                 Key: DRILL-6068
>                 URL: https://issues.apache.org/jira/browse/DRILL-6068
>             Project: Apache Drill
>          Issue Type: New Feature
>    Affects Versions: 1.12.0
>            Reporter: Kunal Khatua
>            Assignee: Kunal Khatua
>            Priority: Major
>              Labels: newbie, ready-to-commit
>             Fix For: 1.13.0
> This is an evolution of the problem stated in DRILL-5741.
> Currently, Drill does not leverage any information about the host machine during start
up and makes assumptions about the available resources (like memory).
> Further more, it is, often, up to the user to define the individual parameters of memory
for Drill: Heap, Direct and CodeCache.
> The idea is to introduce a distribution and user specific configuration checking scripts
(distrib-auto.sh and drill-auto.sh) which follow the same precedence as on the lines of distrib-env.sh
and drill-env.sh.
> A check for the existence of the `distrib-auto.sh` / `drill-auto.sh` scripts will be
performed and executed only if there is any executable lines of code. Otherwise, the expected
behaviour is that the startup functionality Drill will continue as previous versions.
> In combination with the requirement described for DRILL-5741; it would be nice if a starting
up Drillbit could be told upfront on the amount of memory it can assume to access and automatically
perform the allocations for the individual parameters, while providing the ability for users
to override (some or all of) those settings.

This message was sent by Atlassian JIRA

View raw message