Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2986
@Leemoonsoo If no more comments, I will merge it to continue the rest of
the work
---
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2986
Thanks @Leemoonsoo Any more comment ï¼
---
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2986
I'd like to separate Bi-directional RPC and Bi-directional network
connection.
Of course Bi directional RPC of course gives lots of benefits. But
Bi-directional network connection
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2986
For now yarn-cluster mode of spark interpreter is the only use case that
run interpreter process in remote host. And we use property to config the
portRange for the remote spark interpreter
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2986
I was thinking the cases like a (or more) firewalls, NATs between Server
and Interpreters.
And accepting range of ports on each side is more difficult to configure
than accepting a single
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2986
There's 2 properties (`zeppelin.server.rpc.portRange` and
`zeppelin.interpreter.rpc.portRange`) that could be used to constrain the
portRange of zeppelin server rpc and interpreter process rpc.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2986
Thanks @zjffdu for the improvement.
Overall looks good to me. I'd like to see CI goes green before merge while
it change code a lot.
One question. Let's say in the future,
