GitHub user khalidhuseynov reopened a pull request:
https://github.com/apache/zeppelin/pull/1941
[ZEPPELIN-2009] Cron job isn't executed after couple of times
### What is this PR for?
This is to solve the problem with cron job scheduling. basically after
https://github.com/apache/zeppelin/commit/6177c819b1edb76cfaa8f6249dc9041771ce6da9
all empty paragraphs are skipped when executing, but if the paragraph had
status `READY` that status will be stayed same and then the note won't be
considered as terminated in
[here](https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/Notebook.java#L866)
resulting on keeping cron threads up running. So after all 10 threads in the
threadpool are exhausted, new jobs are not scheduled. Here i change the status
of paragraph to `FINISHED` when it's empty and skipping run.
### What type of PR is it?
Bug Fix
### Todos
* [x] - set status to `FINISHED`
### What is the Jira issue?
[ZEPPELIN-2009](https://issues.apache.org/jira/browse/ZEPPELIN-2009)
### How should this be tested?
try to schedule note using cron expression (e.g. `0/5 * * * * ?` every 5
secs) before and after this PR
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/khalidhuseynov/incubator-zeppelin
fix/cron-scheduling
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1941.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1941
----
commit 54e5ce9d7b37cf6fd5c067c0e1455c901a9a10a3
Author: Khalid Huseynov <[email protected]>
Date: 2017-01-25T01:45:55Z
set status FINISHED on empty paragraph
this is required since otherwise notebook wouldn't be isTerminated()
----
---
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.
---
