Github user HeartSaVioR commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/557#issuecomment-167163100
Actually I was trying to restart the interpreter first for each job run via
REST API, but gave up because it throws ```Scheduler already terminated``` when
restarting interpreter and job run is occurred nearly same time.
```
ERROR [2015-12-22 18:05:00,001] ({DefaultQuartzScheduler_Worker-7}
QuartzScheduler.java[schedulerError]:2425) - Job (note.2B83NUA15 threw an
exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See
nested exception: java.lang.RuntimeException: Scheduler already terminated]
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
Caused by: java.lang.RuntimeException: Scheduler already terminated
at
org.apache.zeppelin.scheduler.RemoteScheduler.submit(RemoteScheduler.java:140)
at org.apache.zeppelin.notebook.Note.runAll(Note.java:326)
at
org.apache.zeppelin.notebook.Notebook$CronJob.execute(Notebook.java:391)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
```
After this, I couldn't handle interpreter via UI. Restart doesn't work so I
should kill interpreter via ```kill -9```.
Furthermore, if my understanding is right, interpreter restart aborts
current jobs which are running or pending.
So it would be better to restart interpreter manually.
If we really want to restart interpreter automatically, we should care
about below scenarios.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
