You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Apoorv Naik (JIRA)" <ji...@apache.org> on 2018/07/10 22:10:00 UTC

[jira] [Updated] (ATLAS-2786) [Atlas HA] Zookeeper connection issue

     [ https://issues.apache.org/jira/browse/ATLAS-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Apoorv Naik updated ATLAS-2786:
-------------------------------
    Issue Type: Bug  (was: Improvement)

> [Atlas HA] Zookeeper connection issue
> -------------------------------------
>
>                 Key: ATLAS-2786
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2786
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.8.1, 0.8.2, 1.0.0
>            Reporter: Apoorv Naik
>            Assignee: Apoorv Naik
>            Priority: Critical
>
> The curator client right now only connects to the very first zookeeper server regardless of the number of zookeeper servers provided in the configuration.
>  
> Due to this behavior if the ZK (that Atlas connected to during startup) goes down then Atlas fails to serve further request while constantly trying to reconnect to the dead ZK server.
>  
> This patch makes the change in configuration parsing to allow fallback to different ZK servers in case the primary goes down.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)