Uploaded image for project: 'Zeppelin'
  1. Zeppelin
  2. ZEPPELIN-5625

Potentially misleading error message when sparkR backend is not available

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Trivial
    • Resolution: Fixed
    • 0.10.0
    • 0.10.1, 0.11.0
    • r-interpreter
    • None
    • Zeppelin 0.10.0 binary build

      Ubuntu on AWS

      Linux ip-172-31-85-96 5.4.0-1060-aws #63~18.04.1-Ubuntu SMP Mon Nov 15 14:31:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

    Description

      R interpreter is dying in my 0.10.0 instance, and the message shown in the cell after trying to execute it has the specific suggestion:

      sparkR backend is dead, please try to increase spark.r.backendConnectionTimeout

      This occurs in rlang/src/main/java/org/apache/zeppelin/r/RInterpreter.java:

            // render output with knitr
            if (rbackendDead.get()) {
              return new InterpreterResult(InterpreterResult.Code.ERROR,
                  "sparkR backend is dead, please try to increase spark.r.backendConnectionTimeout");

            if (useKnitr) {
              zeppelinR.setInterpreterOutput(null);

      If this is the real cause of all dead R backends this makes sense; if not, it could be a red herring.

      Attachments

        Activity

          People

            Unassigned Unassigned
            akm Andrew Musselman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 1h
                1h
                Remaining:
                Time Spent - 20m Remaining Estimate - 40m
                40m
                Logged:
                Time Spent - 20m Remaining Estimate - 40m
                20m