You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Ozioma Ihekwoaba (JIRA)" <ji...@apache.org> on 2018/05/01 11:49:00 UTC
[jira] [Updated] (LIVY-465) Client closed before SASL negotiation
finished
[ https://issues.apache.org/jira/browse/LIVY-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ozioma Ihekwoaba updated LIVY-465:
----------------------------------
Issue Type: Bug (was: Question)
> Client closed before SASL negotiation finished
> ----------------------------------------------
>
> Key: LIVY-465
> URL: https://issues.apache.org/jira/browse/LIVY-465
> Project: Livy
> Issue Type: Bug
> Components: Core, RSC, Server
> Affects Versions: 0.4.0
> Environment: Ubuntu 16
> Hadoop 2.7.3
> Hive 2.3.2
> Spark 2.3
> Reporter: Ozioma Ihekwoaba
> Priority: Blocker
>
> Hi all,
> I have been trying to get Livy working for over a week with no results...yet.
> First stump was this error:
> {{Message (nnn bytes) exceeds maximum allowed size (nnn bytes).}}
>
> I set the following in livy.conf and was amazed to discover that Livy DOES NOT load config values from the config file! Or am I missing something?
> {{livy.rsc.rpc.max.size = 1024000000}}
> {{livy.rpc.max.size = 1024000000}}
> {{rpc.max.size = 1024000000}}
>
> NONE of the above was picked up.
> I had to manually edit RSCConf.java and modified thus
>
> {{RPC_MAX_MESSAGE_SIZE("rpc.max.size", 50 * 10 * 1024 * 1024),}}
>
> That took care of that error, now I'm stuck with this
> {{utils.LineBufferedStream: stdout: Exception in thread "main" java.util.concurrent.ExecutionException: javax.security.sasl.SaslException:}}
> {{ Client closed before SASL negotiation finished.}}
> I have 3 builds now for Spark 1.6 and 2.2, still with the same endless cycle of exceptions.
> What could be wrong?
> Is it really hard to get Livy working a machine?
> And WHY is Livy not picking config values from livy.conf???
>
> Thanks,
> Ozioma
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)