[
https://issues.apache.org/jira/browse/ASTERIXDB-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300521#comment-16300521
]
ASF subversion and git services commented on ASTERIXDB-2207:
------------------------------------------------------------
Commit d90723359740d71df4a4d671d311716dac5495cb in asterixdb's branch
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=d907233 ]
[ASTERIXDB-2207][CLUS] Introduce Coordination Service API
- user model changes: no
- storage format changes: no
- interface changes: yes
- Add ICoordinationService to CC and NC
application context.
Details:
- Add API to support coordination service.
- An initial no-op implementation of coordination
service.
Change-Id: I8670e3498a141029d21826a2908033510c749838
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2244
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Michael Blow <[email protected]>
> Coordination Service API
> ------------------------
>
> Key: ASTERIXDB-2207
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2207
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: CLUS - Cluster management
> Reporter: Murtadha Hubail
> Assignee: Murtadha Hubail
>
> Currently we use CC as our cluster coordinator. However, if we lose the CC
> node, all information about the cluster is lost. To overcome this,
> distributed applications typically have a distributed coordination service
> (i.e ZooKeeper) that can store and persist metadata about the cluster. We
> need to introduce coordination service API to allow for such extension to the
> system.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
