You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Xun Liu (JIRA)" <ji...@apache.org> on 2019/03/07 09:01:02 UTC
[jira] [Created] (ZEPPELIN-4039) Fix restart interpreter process
ConcurrentModificationException
Xun Liu created ZEPPELIN-4039:
---------------------------------
Summary: Fix restart interpreter process ConcurrentModificationException
Key: ZEPPELIN-4039
URL: https://issues.apache.org/jira/browse/ZEPPELIN-4039
Project: Zeppelin
Issue Type: Bug
Components: zeppelin-interpreter
Affects Versions: 0.9.0
Reporter: Xun Liu
Assignee: Xun Liu
Fix For: 0.9.0
Attachments: restart-interpreter-ConcurrentModificationException.gif
1) I set it in zeppeln-env.sh
Export ZEPPELIN_FORCE_STOP=true
2) I create an interpreter process container in the remote YARN.
3) When I restart this interpreter, The interpreter process container will have a ConcurrentModificationException and will not exit properly.
The reason for starting this BUG is:
When exporting ZEPPELIN_FORCE_STOP=true,
Restart the interpreter process, the zeppelin server will execute the session that closes the process.
At the same time, the shutdown() and process() will be remote call.
In the RemoteInterpreterServer, the shutdown() and close() functions do not have concurrency control on the interpreterGroup. Causes an exception.
!restart-interpreter-ConcurrentModificationException.gif|width=866,height=598!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)