[
https://issues.apache.org/jira/browse/ATLAS-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-998:
-----------------------------------
Fix Version/s: 0.7.1-incubating
Committed to 0.7-incubating branch:
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0ada3940ea7628271b062339dd27a22b1e4e5463
> Atlas should determine HA mode from property atlas.server.ids, instead of
> atlas.server.ha.enabled
> -------------------------------------------------------------------------------------------------
>
> Key: ATLAS-998
> URL: https://issues.apache.org/jira/browse/ATLAS-998
> Project: Atlas
> Issue Type: Bug
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-998-final.patch, ATLAS-998.3.patch, ATLAS-998.patch
>
>
> Atlas server uses the value of property 'atlas.server.ha.enabled' to
> determine if Atlas is running in High-Available mode or not. Another property
> 'atlas.server.ids' lists all the server instances configured to run in the
> cluster. This and other related properties are used to determine if a server
> should be run in active or pass mode.
> Instead of using 2 different properties, Atlas can determine if HA mode is
> enabled or not by looking at the number of instances listed in
> 'atlas.server.ids' property. When multiple instances are listed in this
> property, Atlas will run in HA mode; else it will run in stand-alone mode.
> Using a single property might be less confusing to manage and troubleshoot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
