ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-22021) Livy not working with the default configuration
Date Fri, 22 Sep 2017 07:57:00 GMT

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

Hudson commented on AMBARI-22021:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8120 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8120/])
AMBARI-22021.Livy not working with the default configuration(Prabhjyot (venkatasairam.lanka:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d221ab786277abf6d8e9e8dbc9442e37423484a4])
* (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/livy2_config_template.py
* (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/interpreter_json_template.py


> Livy not working with the default configuration
> -----------------------------------------------
>
>                 Key: AMBARI-22021
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22021
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Prabhjyot Singh
>            Assignee: Prabhjyot Singh
>             Fix For: 3.0.0, 2.6.0
>
>         Attachments: AMBARI-22021_trunk_v1.patch, AMBARI-22021_trunk_v2.patch
>
>
> This started failing with ZEPPELIN-2909, which introduces `"className": "org.apache.zeppelin.livy.LivySharedInterpreter".
and now Livy fails with following exception;
> {code:java}
> java.lang.NullPointerException
> 	at org.apache.zeppelin.livy.BaseLivyInterpreter.open(BaseLivyInterpreter.java:109)
> 	at org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
> 	at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:493)
> 	at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
> 	at org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> {code}



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

Mime
View raw message