You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by liuxunorg <gi...@git.apache.org> on 2018/10/06 02:03:53 UTC
[GitHub] zeppelin pull request #3203: [ZEPPELIN-3626] Cluster server and client modul...
GitHub user liuxunorg opened a pull request:
https://github.com/apache/zeppelin/pull/3203
[ZEPPELIN-3626] Cluster server and client module design
### What is this PR for?
The cluster management server uses the Raft algorithm library Atomix to form a service cluster with consistent service status in the Zeppelin cluster. The cluster management client connects to the cluster management server for metadata operations of services and processes. The cluster monitoring module checks if each Zeppelin-Server and Zeppelin Interpreter process in the cluster is active.
[Feature]
* [x] add cluster manager server
* [x] add cluster manager client
* [x] add cluster monitor
* [x] add cluster create Interpreter thrift interface
* [x] add InterpreterFactoryInterface
* [x] add the function call in the ZeppelinServer startup cluster
* https://issues.apache.org/jira/browse/ZEPPELIN-3626
CI pass
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? [Design document](https://docs.google.com/document/d/1a8QLSyR3M5AhlG1GIYuDTj6bwazeuVDKCRRBm-Qa3Bw/edit#heading=h.qbcgqhd0wwh8)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liuxunorg/zeppelin ZEPPELIN-3626
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/3203.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3203
----
commit 6f9ebe2ec6572bf8f1d0c94635f1a63b025df123
Author: liuxunorg <33...@...>
Date: 2018-10-01T13:51:35Z
[ZEPPELIN-3626] Cluster server and client module design
The cluster management server uses the Raft algorithm library Atomix to form a service cluster with consistent service status in the Zeppelin cluster. The cluster management client connects to the cluster management server for metadata operations of services and processes. The cluster monitoring module checks if each Zeppelin-Server and Zeppelin Interpreter process in the cluster is active.
[Feature]
* [x] add cluster manager server
* [x] add cluster manager client
* [x] add cluster monitor
* [x] add cluster create Interpreter thrift interface
* [x] add InterpreterFactoryInterface
* [x] add the function call in the ZeppelinServer startup cluster
* https://issues.apache.org/jira/browse/ZEPPELIN-3626
CI pass
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? [Design document](https://docs.google.com/document/d/1a8QLSyR3M5AhlG1GIYuDTj6bwazeuVDKCRRBm-Qa3Bw/edit#heading=h.qbcgqhd0wwh8)
----
---
[GitHub] zeppelin issue #3203: [ZEPPELIN-3626] Cluster server and client module desig...
Posted by liuxunorg <gi...@git.apache.org>.
Github user liuxunorg commented on the issue:
https://github.com/apache/zeppelin/pull/3203
@zjffdu , I modified `guava.version` in `zeppelin-interpreter/pom.xml`. JOB3 and JOB7 in [travis CI](https://travis-ci.org/liuxunorg/zeppelin/builds/435675452) failed, please help me solve it, thank you!
---