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 Mon, 08 Jan 2018 18:03:00 GMT


ASF subversion and git services commented on ASTERIXDB-2207:

Commit ab1013cb90d3ebaba0b55821215eb927fb0b5478 in asterixdb's branch refs/heads/master from
[;h=ab1013c ]

[ASTERIXDB-2207][CLUS] Add Delete API to ICoordinationService

- user model changes: no
- storage format changes: no
- interface changes: yes
  - Add delete to ICoordinationService

Change-Id: Ie3a17fb1cec9350025cdf0ee340c80d7e0f1a9f0
Sonar-Qube: Jenkins <>
Tested-by: 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