GitHub user wary opened a pull request: https://github.com/apache/zeppelin/pull/2404
fix bugs for: when interpreter setting start, all user running aborted ### What is this PR for? A few sentences describing the overall goals of the pull request's commits. First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html ### What type of PR is it? [Bug Fix] ### Todos * [ ] - Task ### What is the Jira issue? [ZEPPELIN-2638] (https://issues.apache.org/jira/browse/ZEPPELIN-2638) ### How should this be tested? context: running zeppelin in multi user environment and the option of the spark interpreter is "The interpreter will be instantiated Per User in isolated process"; before fix: when one user restart spark interpreter on his note configuration pageï¼all running jobs of other users has also been aborted after fix: when one user restart spark interpreter on his note configuration pageï¼only the running jobs of the user who restart interpreter aborted, there is no impact to the jobs of other users ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? * Is there breaking changes for older versions? * Does this needs documentation? You can merge this pull request into a Git repository by running: $ git pull https://github.com/wary/zeppelin bugs-fix-interpreter-restart Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2404.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 #2404 ---- commit fad3348a64e38d63a6ff6e988960ac6b994ef815 Author: lei wang <lei1...@outlook.com> Date: 2017-06-11T07:54:50Z fix bugs for: when interpreter setting start, all user running aborted ---- --- 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. ---