[LIVY-459] First submission via livy-python-api fails with KryoException, subsequent retries succeed - ASF JIRA

Attach files

Attach Screenshot

Add vote

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 0.5.0, 0.6.0
Fix Version/s: 0.9.0
Component/s: None
Labels:
None
Environment:
Red Hat Enterprise Linux Server release 7.3 (Maipo)
java version "1.8.0_141"

Description

I have the following code:

from livy.client import HttpClient


def foobar(ctx):
    return ctx.sc.parallelize(range(101)).mean()


client = HttpClient('http://r2i0n33:8998')
try:
    print(client.submit(foobar).result())
except Exception as e:
    print(e)
print(client.submit(foobar).result())
client.stop(True)

failing with the following error:

org.apache.livy.shaded.kryo.kryo.KryoException: Encountered unregistered class ID: 510
org.apache.livy.shaded.kryo.kryo.util.DefaultClassResolver.readClass(DefaultClassResolver.java:119)
org.apache.livy.shaded.kryo.kryo.Kryo.readClass(Kryo.java:656)
org.apache.livy.shaded.kryo.kryo.Kryo.readClassAndObject(Kryo.java:767)
org.apache.livy.client.common.Serializer.deserialize(Serializer.java:63)
org.apache.livy.rsc.driver.BypassJob.call(BypassJob.java:39)
org.apache.livy.rsc.driver.BypassJob.call(BypassJob.java:27)
org.apache.livy.rsc.driver.JobWrapper.call(JobWrapper.java:57)
org.apache.livy.rsc.driver.BypassJobWrapper.call(BypassJobWrapper.java:42)
org.apache.livy.rsc.driver.BypassJobWrapper.call(BypassJobWrapper.java:27)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)
50.0

Is this to be expected? I would have thought that the first submission should work already. I did not find this behavior online/in the mailing list archives. Any pointers how to resolve this?

This happens in both the livy-0.5.0 binaries and the github master, on RedHat EL 7.3.