[
https://issues.apache.org/jira/browse/ATLAS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228335#comment-15228335
]
venkata madugundu commented on ATLAS-603:
-----------------------------------------
Hi Hemanth,
I was going through the changes that need to be done in
atlas-application.properties for enabling HA. I had few questions.
If one were to stand up an ensemble of 3 Atlas instances for automated HA
failover...
a) For each instance of Atlas, its atlas-application.properties should have
something like...
atlas.server.ids=id1,id2, id3
atlas.server.address.id1=host1.company.com:21000
atlas.server.address.id2=host2.company.com:21000
atlas.server.address.id3=host3.company.com:21000
Is that right ?
May be it can be made flexible in later updates to probably register each Atlas
instance as an ephemeral znode with ZK so that all the server info need not be
specified in atlas-application.properties. That would make it easier from
operations point of view.
Is there a current mechanism to specify those properties as say "java system
properties" when Atlas is started with atlas_start.py script ?
> Document High Availability of Atlas
> -----------------------------------
>
> Key: ATLAS-603
> URL: https://issues.apache.org/jira/browse/ATLAS-603
> 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
(v6.3.4#6332)
