drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-4741) sqlline scripts should differentiate embedded vs remote config
Date Tue, 21 Jun 2016 19:03:57 GMT
Paul Rogers created DRILL-4741:
----------------------------------

             Summary: sqlline scripts should differentiate embedded vs remote config
                 Key: DRILL-4741
                 URL: https://issues.apache.org/jira/browse/DRILL-4741
             Project: Apache Drill
          Issue Type: Improvement
    Affects Versions: 1.8.0
            Reporter: Paul Rogers
            Priority: Minor


$DRILL_HOME/bin contains four sqlline-related scripts:

sqlline -- main script for running sqlline
drill-conf — Wrapper for sqlline, uses drill config to find Drill. Seems this one needs
fixing to use a config other than the hard-coded $DRILL_HOME/conf location.
drill-embedded — Starts a drill “embedded” in SqlLine, using a local ZK.
drill-localhost — Wrapper for sqlline, uses a local ZK.

The last three turn around and call sqlline.

Behind the scenes, the script call drill-config.sh and drill-env.sh to do setup.

Note, however that we run Sqlline and Drill in three distinct configurations:

sqlline as client: should run with light memory
drillbit as daemon: should run with full memory use
sqline with embedded drillbit: sqlline needs to run with Drillbit memory options.

Today, sqlline always uses the Drillbit memory options (and VM options) which results in too
much memory and port conflicts when running client-only.

Provide sqlline specific VM and memory options. Then, the tricky bit, use them only when Drill
is not embedded.



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

Mime
View raw message