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/07/15 14:21:59 UTC

[GitHub] zeppelin pull request #3072: Zeppelin 3610

GitHub user liuxunorg opened a pull request:

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

    Zeppelin 3610

    ## [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] added support for checking lambda syntax styles in the pom.xml file
    * [x] add raft algorithm copycat jar
    * [x] add  Cluster State Machine
    * [x] add state machine query command
    * [x] add state machine delete command
    * [x] add state machine put command
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-3610
    
    ### How should this be tested?
    CI pass
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No

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/3072.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 #3072
    
----
commit 74ff022efcddae7a70f1a833409da693c84f9f6c
Author: liuxunorg <33...@...>
Date:   2018-07-14T03:25:18Z

    [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
    
    - - Added support for checking lambda syntax styles in the pom.xml file
      - add raft algorithm copycat jar
      - add  Cluster State Machine
      - add state machine query command
      - add state machine delete command
      - add state machine put command
    
    What is the Jira issue?
    
    - https://issues.apache.org/jira/browse/ZEPPELIN-3610
    
    How should this be tested?
    
    CI pass
    
    Screenshots (if appropriate)
    
    Questions:
    
    - Does the licenses files need update? No
    - Is there breaking changes for older versions? No
    - Does this needs documentation? No

commit e99d51c3ad201fb445d55b601ef8a2e6edad035e
Author: liuxunorg <33...@...>
Date:   2018-07-14T03:25:18Z

    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] added support for checking lambda syntax styles in the pom.xml file
    * [x] add raft algorithm copycat jar
    * [x] add  Cluster State Machine
    * [x] add state machine query command
    * [x] add state machine delete command
    * [x] add state machine put command
    
    * 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? No

commit 7fde5e869eca491fc5e2a9aa307c627183a03379
Author: liuxunorg <33...@...>
Date:   2018-07-14T08:59:10Z

    Merge branch 'ZEPPELIN-3610' of https://github.com/liuxunorg/zeppelin into ZEPPELIN-3610

commit 5af211ea1fd986538cd7f11719dfaa5f5f80bcd2
Author: liuxunorg <33...@...>
Date:   2018-07-14T11:09:03Z

    delete ClusterManagerServer

commit c4c07cd123e1ad31665409b7dc18f8fab8c892f2
Author: liuxunorg <33...@...>
Date:   2018-07-14T12:12:42Z

    delete netty jar

commit 3fcf6a6ce2c7bd351dfd43bc05aa5b34e79d7232
Author: liuxunorg <33...@...>
Date:   2018-07-14T14:00:45Z

    delete  netty-all jar.

commit e32651f56d4acda36e49d7d3f3ac5cc249ab0e80
Author: liuxunorg <33...@...>
Date:   2018-07-15T01:40:38Z

    exclusion slf4j

----


---

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

Posted by liuxunorg <gi...@git.apache.org>.
Github user liuxunorg closed the pull request at:

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


---