[jira] [Created] (ZEPPELIN-5625) Potentially misleading error message when sparkR backend is not available

["Andrew Musselman (Jira)" <ji...@apache.org>]

Andrew Musselman created ZEPPELIN-5625:
------------------------------------------

             Summary: Potentially misleading error message when sparkR backend is not available
                 Key: ZEPPELIN-5625
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5625
             Project: Zeppelin
          Issue Type: Improvement
          Components: r-interpreter
    Affects Versions: 0.10.0
         Environment: 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
            Reporter: Andrew Musselman
             Fix For: 0.10.1


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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)