[GitHub] zeppelin pull request #3183: [ZEPPELIN-3610] Cluster Raft module design

2018-09-27 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/3183


---


[GitHub] zeppelin pull request #3183: [ZEPPELIN-3610] Cluster Raft module design

2018-09-19 Thread liuxunorg
GitHub user liuxunorg opened a pull request:

https://github.com/apache/zeppelin/pull/3183

[ZEPPELIN-3610] Cluster Raft module design

### What is this PR for?

By using the Raft protocol, multiple Zeppelin-Server groups are built into 
a Zeppelin cluster, the cluster State Machine is maintained through the Raft 
protocol, and the services in the cluster are agreed upon. The Zeppelin-Server 
and Zeppelin-Interperter services and processes are stored in the Cluster 
MetaData. Metadata information;

### What type of PR is it?
[Feature]

### Todos
* [x] add raft algorithm atomix jar
* [x] add cluster state machine
* [x] add state machine query command
* [x] add state machine delete command
* [x] add state machine put command
* [x] Isolate the netty JAR package introduced by atomix

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-3610

### How should this be tested?
[CI pass](https://travis-ci.org/liuxunorg/zeppelin/builds/418742522)

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? Yes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/liuxunorg/zeppelin ZEPPELIN-3610

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/3183.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 #3183


commit f25005f52322c076d20d25c0319a59b528a5a16f
Author: liuxunorg <33611720@...>
Date:   2018-08-21T14:57:44Z

Cluster Raft module design

By using the Raft protocol, multiple Zeppelin-Server groups are built into 
a Zeppelin cluster, the cluster State Machine is maintained through the Raft 
protocol, and the services in the cluster are agreed upon. The Zeppelin-Server 
and Zeppelin-Interperter services and processes are stored in the Cluster 
MetaData. Metadata information;

[Feature]

* [x] add raft algorithm atomix jar
* [x] add cluster state machine
* [x] add state machine query command
* [x] add state machine delete command
* [x] add state machine put command
* [x] Isolate the netty JAR package introduced by atomix

* https://issues.apache.org/jira/browse/ZEPPELIN-3610

CI pass

* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? Yes




---