GitHub user zhongneu opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/760
[ZEPPELIN-716] protect the whole spark repl init process
### What is this PR for?
ZeppelinContext may not be initialized properly in concurrent mode:
When I create & run multiple notebooks using rest API concurrently, I can
see such errors if the jobs trying to use ZeppelinContext:
```
<console>:23: error: not found: value z
```
I think this issue can be reproduced by:
1. create 4 - 5 new notebooks with content: `println(z)`
2. use rest API to run the newly created notebooks concurrently
It seems the issue is gone after I expand the lock to protect the whole
process of spark REPL initializing / binding.
### What type of PR is it?
Bug Fix
### Todos
### What is the Jira issue?
[ZEPPELIN-717](https://issues.apache.org/jira/browse/ZEPPELIN-717)
### How should this be tested?
1. create 4 - 5 new notebooks with content: `println(z)`
2. use rest API to run the newly created notebooks concurrently
### 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/zhongneu/incubator-zeppelin
protect-spark-repl-init
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/760.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 #760
----
commit 3022612af45df141ce5bbfa242048e04b0fe6d7a
Author: Zhong Wang <wangzhong....@gmail.com>
Date: 2016-03-04T07:00:43Z
protect the whole spark repl init process
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
