You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Ruslan Dautkhanov (JIRA)" <ji...@apache.org> on 2018/02/19 23:37:01 UTC

[jira] [Created] (ZEPPELIN-3247) Restart grpc stream for each paragraph run

Ruslan Dautkhanov created ZEPPELIN-3247:
-------------------------------------------

             Summary: Restart grpc stream for each paragraph run
                 Key: ZEPPELIN-3247
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3247
             Project: Zeppelin
          Issue Type: Bug
          Components: Core, pySpark, python-interpreter, zeppelin-interpreter, zeppelin-server
    Affects Versions: 0.7.3, 0.8.0
            Reporter: Ruslan Dautkhanov


Please read [https://github.com/grpc/grpc-java/issues/4086] for details
|The RPC (a.k.a. the stream) cannot continue, but you can start a new RPC. The Channel will still work. You can start a new RPC on the existing channel. Without seeing the code I don't know why a failed RPC would fail the whole application, but that isn't the intended behavior.|
 
It seems spark interpreter --> grpc --> ipython backend is currently somewhat brittle as any exception stops grpc stream [1].
 
Would it be possible to adjust code in ipython logic to restart grpc stream for each paragraph run ? To make new ipython logic more robust.
 
 
 
 
[1]
 
{quote}INFO [2018-02-14 10:39:10,923] (\{grpc-default-worker-ELG-1-2} AbstractClientStream2.java[inboundDataReceived]:249) - Received data on closed stream
INFO [2018-02-14 10:39:10,924] (\{grpc-default-worker-ELG-1-2} AbstractClientStream2.java[inboundDataReceived]:249) - Received data on closed stream
INFO [2018-02-14 10:39:10,925] (\{grpc-default-worker-ELG-1-2} AbstractClientStream2.java[inboundDataReceived]:249) - Received data on closed stream
{quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)