Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 6 Feb 2017 19:29:41 +0000 (UTC)
From: "Siddharth Seth (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13036771.1484969476000.8524.1486409381688@Atlassian.JIRA>
In-Reply-To: <JIRA.13036771.1484969476000@Atlassian.JIRA>
References: <JIRA.13036771.1484969476000@Atlassian.JIRA> <JIRA.13036771.1484969476467@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HIVE-15688) LlapServiceDriver - an option to
 start the cluster immediately
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 06 Feb 2017 19:29:49 -0000


    [ https://issues.apache.org/jira/browse/HIVE-15688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854591#comment-15854591 ] 

Siddharth Seth commented on HIVE-15688:
---------------------------------------

Right. Missed that.
Are we ignoring the OUTPUT_DIR specified by the user in that case?

> LlapServiceDriver - an option to start the cluster immediately
> --------------------------------------------------------------
>
>                 Key: HIVE-15688
>                 URL: https://issues.apache.org/jira/browse/HIVE-15688
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-15688.01.patch, HIVE-15688.patch
>
>
> run.sh is very slow because it's 4 calls to slider, which means 4 JVMs, 4 connections to RM and other crap, for   2-5sec. of overhead per call, depending on the machine/cluster.
> What we need is a mode for llapservicedriver that would not generate run.sh, but would rather run the cluster immediately by calling the corresponding 4 slider APIs. Should probably be the default, too. For compat with scripts we might generate blank run.sh for now.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)