Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 16 Jun 2017 09:42:00 +0000 (UTC)
From: "Prabhjyot Singh (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13079725.1497438557000.32329.1497606120140@Atlassian.JIRA>
In-Reply-To: <JIRA.13079725.1497438557000@Atlassian.JIRA>
References: <JIRA.13079725.1497438557000@Atlassian.JIRA> <JIRA.13079725.1497438557869@jira-lw-us.apache.org>
Subject: [jira] [Updated] (AMBARI-21243) Improve Zeppelin startup time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 16 Jun 2017 09:42:04 -0000


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

Prabhjyot Singh updated AMBARI-21243:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Improve Zeppelin startup time
> -----------------------------
>
>                 Key: AMBARI-21243
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21243
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Prabhjyot Singh
>            Assignee: Prabhjyot Singh
>         Attachments: AMBARI-21243-trunk-v1.patch
>
>
> Currently Zeppelin takes more than 1 minute to start. The bulk of the time during startup is spent with 
> {code}
> 2017-05-09 09:07:34,636 - Will retry 29 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:07:39,639 - Will retry 28 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:07:44,644 - Will retry 27 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:07:49,649 - Will retry 26 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:07:54,652 - Will retry 25 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:07:59,653 - Will retry 24 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:08:05,885 - Will retry 23 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:08:10,890 - Will retry 22 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:08:15,892 - Will retry 21 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:08:20,893 - Will retry 20 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:08:25,894 - Will retry 19 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:08:30,899 - Will retry 18 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> 2017-05-09 09:08:35,904 - Will retry 17 time(s), caught exception: interpreter.json not found. waiting for Zeppelin server to start.... Sleeping for 5 sec(s)
> {code}
> So the idea of this is to have interpeter.json cached, and apply it does not exists.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)