Uploaded image for project: 'Zeppelin'
  1. Zeppelin
  2. ZEPPELIN-2645

Adding way to register RemoteInterpreterServer's port into InterpreterProcess

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.8.0
    • 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

          New Feature - A new feature of the product, which has yet to be developed. ZEPPELIN-2040 ClusterManager to support launching interpreter in a cluster

          • Major - Major loss of function.
          • In Progress

          Improvement - An improvement or enhancement to an existing feature or task. ZEPPELIN-2035 BI directional RPC framework between ZeppelinServer and InterpreterProcess on top of thrift

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          links to

          Web Link GitHub Pull Request #2410

          Web Link GitHub Pull Request #2418

          Web Link GitHub Pull Request #2562

          Activity

            People

              jongyoul Jongyoul Lee
              jongyoul Jongyoul Lee
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: