atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <>
Subject [jira] [Commented] (ATLAS-603) Document High Availability of Atlas
Date Wed, 06 Apr 2016 15:00:29 GMT


Hemanth Yamijala commented on ATLAS-603:

a) Yes. That is the way to specify.

I use Curator's LeaderLatch recipe to elect a leader that would become the Active. LeaderLatch
requires each instance to have a unique Identifier. That's the reason why we need the IDs.
Secondly, we wanted to keep the same configuration for all instances - as it makes it easier
to distribute the configuration using systems like Ambari. In order to enable that, I needed
a way by which I could list all the IDs in the same config file, but still have each server
pick one instance up based on the address it is bound to. Could you perhaps explain how I
can achieve thisusing the ephemeral znode scheme? If there's a feasible solution, we could
certainly discuss it.

Currently there's no way specify it as part of system properties, but it should be doable.
Did you want it only for the server IDs? Maybe you have a specific use case in mind? It would
be great if you could explain that.

> Document High Availability of Atlas
> -----------------------------------
>                 Key: ATLAS-603
>                 URL:
>             Project: Atlas
>          Issue Type: Sub-task
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>         Attachments: ATLAS-603.patch
> The document:
> * Mechanism
> * Config items
> * Client changes.

This message was sent by Atlassian JIRA

View raw message