You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Glenn Thomas (Jira)" <ji...@apache.org> on 2021/03/25 22:12:00 UTC

[jira] [Commented] (LIVY-636) Unable to create interactive session with additional JAR in spark.driver.extraClassPath

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

Glenn Thomas commented on LIVY-636:
-----------------------------------

I can confirm that the solution offered by [~yuuya] solved the issue for us, though the paths were slightly different.

It seems the issue is that is the `scala-library-\{version}.jar` not being included when interactive spark sessions are launched? Once this jar is included in the `livy.repl.jars` config along with the normal REPL jars the issue is resolved.

 

Is this a bug in Livy itself, or common deployments of Livy (eg. AWS EMR) ? 

> Unable to create interactive session with additional JAR in spark.driver.extraClassPath
> ---------------------------------------------------------------------------------------
>
>                 Key: LIVY-636
>                 URL: https://issues.apache.org/jira/browse/LIVY-636
>             Project: Livy
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Ishita Virmani
>            Priority: Major
>         Attachments: applicationmaster.log, container.log, stacktrace.txt, test.png
>
>
> Command Run: c{{url -H "Content-Type: application/json" -X POST -d '\{"kind":"pyspark","conf":{"spark.driver.extraClassPath":"/data/XXX-0.0.1-SNAPSHOT.jar"}}' -i http://<LIVY_SERVER_IP:PORT>/session}}
> {{The above command fails to create a Spark Session on YARN with Null pointer exception. Stack trace for the same has been attached along-with.}}
> The JAR file here is present on local driver Path. Also tried using HDFS path in the following manner {{hdfs://<NM_IP>:<NM_Port>/data/XXX-0.0.1-SNAPSHOT.jar}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)