Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
From now, the port of interpreter is fixed by Zeppelin server, and which connect interpreter via this port. But it's not fragile running interpreter remotely. Then I suggest reverse way to pass the port information from interpreter to server. It require one more communication channel and I'll use netty for it. This issue is initialized from ZEPPELIN-2035 and related to ZEPPELIN-2040.
Attachments
Issue Links
- is related to
-
ZEPPELIN-2040 ClusterManager to support launching interpreter in a cluster
- In Progress
-
ZEPPELIN-2035 BI directional RPC framework between ZeppelinServer and InterpreterProcess on top of thrift
- Closed
- links to