GitHub user OopsOutOfMemory opened a pull request:
https://github.com/apache/zeppelin/pull/1888
[ZEPPELIN-1941] Fix deadlock in cron job
### What is this PR for?
There is a deadlock in concurrent cron job execution with release resource
option.
Scenario:
Two notebook
GitHub user OopsOutOfMemory opened a pull request:
https://github.com/apache/zeppelin/pull/1891
[ZEPPELIN-1941] Fix cron job with release resource option dead lock
### What is this PR for?
There is a deadlock in concurrent cron job execution with release resource
option
Github user OopsOutOfMemory commented on the issue:
https://github.com/apache/zeppelin/pull/1891
we already a test case for this
https://github.com/apache/zeppelin/blob/9e75f5b50ac1573d423fa937b801df77d6a36f3c/zeppelin-zengine/src/test/java/org/apache/zeppelin/notebook
Github user OopsOutOfMemory commented on the issue:
https://github.com/apache/zeppelin/pull/1891
It seems CI has a network issue
```
[ERROR] Error requesting archive.
[ERROR] Status: 503
[ERROR] Request options: {
[ERROR] "uri":
"https://gi
Github user OopsOutOfMemory commented on the issue:
https://github.com/apache/zeppelin/pull/1891
I'm not sure, this PR is intent to fix the dead lock issue.
---
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 pr
Github user OopsOutOfMemory commented on the issue:
https://github.com/apache/zeppelin/pull/1891
Flaky test may be another concurrency issue in scheduler execute jobs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user OopsOutOfMemory commented on the issue:
https://github.com/apache/zeppelin/pull/1891
@Leemoonsoo @jongyoul Any comments for this PR ?
---
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
