Zeppelin 错误：部署到 Kubernetes 集群后出现“解释器进程未运行”

Posted 2023-03-23

【中文标题】Zeppelin 错误：部署到 Kubernetes 集群后出现“解释器进程未运行”

【英文标题】：Zeppelin Error: "Interpreter process is not running" after delploy to Kubernetes Cluster

【发布时间】：2020-08-04 22:58:25

【问题描述】：

我是这些 docker、kubernetes 和 zeppelin 的新手。 目前我将一个docker镜像部署到kubernetes集群，当我尝试运行一个非常简单的python代码时，它给出了以下错误，我检查了解释器，它们都是绿色的，有人知道可能的原因是什么？谢谢，还附上我正在使用的yaml文件

org.apache.zeppelin.interpreter.InterpreterException: java.io.IOException: Interpreter process is not running
null
    at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.open(RemoteInterpreter.java:134)
    at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:298)
    at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:431)
    at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:74)
    at org.apache.zeppelin.scheduler.Job.run(Job.java:172)
    at org.apache.zeppelin.scheduler.AbstractScheduler.runJob(AbstractScheduler.java:130)
    at org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:159)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Interpreter process is not running
null
    at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.internal_create(RemoteInterpreter.java:166)
    at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.open(RemoteInterpreter.java:131)
    ... 13 more

Yaml 文件：

apiVersion: apps/v1
kind: Deployment
metadata:
  name: zeppelin-spark
spec:
  replicas: 1
  selector:
    matchLabels:
      app: zeppelin-spark
  template:
    metadata:
      labels:
        app: zeppelin-spark
    spec:
      containers:
      - name: zeppelin-spark
        image: 411028718373.dkr.ecr.us-east-1.amazonaws.com/zeppelin:official
        command: [ "/bin/bash", "-ce", "tail -f /dev/null" ]
        resources:
          limits:
            memory: "4Gi"
          requests:
            memory: "2Gi"
        # volumeMounts:
        # - mountPath: "/media"
        #   name: test-volume
        ports:
        - containerPort: 8080
      # volumes:
      # - name: test-volume
      #   persistentVolumeClaim:
      #     claimName: test-volume

【问题讨论】：

你解决了吗？？

【参考方案1】：

转到zeppeline web ui并单击右上角的设置图标，然后选择正确的解释器并将其拖到“解释器绑定”区域的顶部位置，保存并再次尝试运行该段落。