You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Prabhjyot Singh (JIRA)" <ji...@apache.org> on 2017/06/14 11:10:00 UTC

[jira] [Created] (AMBARI-21243) Improve Zeppelin startup time

Prabhjyot Singh created AMBARI-21243:
----------------------------------------

             Summary: 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


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)