asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ASTERIXDB-2207) Coordination Service API
Date Thu, 21 Dec 2017 20:17:03 GMT


ASF subversion and git services commented on ASTERIXDB-2207:

Commit d90723359740d71df4a4d671d311716dac5495cb in asterixdb's branch refs/heads/master from
[;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.

- Add API to support coordination service.
- An initial no-op implementation of coordination

Change-Id: I8670e3498a141029d21826a2908033510c749838
Sonar-Qube: Jenkins <>
Tested-by: Jenkins <>
Contrib: Jenkins <>
Integration-Tests: Jenkins <>
Reviewed-by: Michael Blow <>

> Coordination Service API
> ------------------------
>                 Key: ASTERIXDB-2207
>                 URL:
>             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

View raw message