Uploaded image for project: 'Livy'
  1. Livy
  2. LIVY-465

Client closed before SASL negotiation finished

    XMLWordPrintableJSON

    Details

    • Type: Question
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.4.0
    • Fix Version/s: None
    • Component/s: Core, RSC, Server
    • Labels:
      None
    • Environment:
      Ubuntu 16
      Hadoop 2.7.3
      Hive 2.3.2
      Spark 2.3

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ozioma Ozioma Ihekwoaba
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: