ambari-issues mailing list archives

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

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

Hadoop QA commented on AMBARI-22021:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12888280/AMBARI-22021_trunk_v2.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level [trunk compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12311//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12311//console

This message is automatically generated.

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