You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/07/14 01:14:00 UTC

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

    [ https://issues.apache.org/jira/browse/ATLAS-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543914#comment-16543914 ] 

ASF subversion and git services commented on ATLAS-2786:
--------------------------------------------------------

Commit 28e5d5d9cd6ed94e121d02d49cad01b14b02dc1c in atlas's branch refs/heads/branch-1.0 from apoorvnaik
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=28e5d5d ]

ATLAS-2786: Honor ZK server ensemble provided in configuration

Change-Id: I3153f258276b534e864fb53b8bcc1cd6af936b5b


> [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
>         Attachments: 0001-ATLAS-2786-Honor-ZK-server-ensemble-provided-in-conf.patch
>
>
> 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)