Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A489FC470 for ; Fri, 16 Jan 2015 02:34:33 +0000 (UTC) Received: (qmail 93523 invoked by uid 500); 16 Jan 2015 02:34:35 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 93488 invoked by uid 500); 16 Jan 2015 02:34:35 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 93369 invoked by uid 99); 16 Jan 2015 02:34:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jan 2015 02:34:35 +0000 Date: Fri, 16 Jan 2015 02:34:35 +0000 (UTC) From: "Denis Petrov (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-3485) accumulo client tries to connect only to the first ZK in the list, making it SPOF MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Petrov updated ACCUMULO-3485: ----------------------------------- Description: Accumulo client tries to connect only to the first ZK server. if that single ZK server is down, the accumulo client does not try other ZK servers. Thus the first ZK is single point of failure, if it is down, accumulo client cannot work {code:java} val instance = new ZooKeeperInstance("zzz", "no-zk-here.example.com,zk1.example.com,zk2.example.com,zk3.example.com") val conn = instance.getConnector("root", "pass".getBytes) println("db connected, tables=" + conn.tableOperations.list) {code} was: Accumulo client libraries tries to connect only to the first ZK server. if that single ZK server is down, the accumulo client does not try other ZK servers. Thus the first ZK is single point of failure, if it is down, accumulo client cannot work {code:java} val instance = new ZooKeeperInstance("zzz", "no-zk-here.example.com,zk1.example.com,zk2.example.com,zk3.example.com") val conn = instance.getConnector("root", "pass".getBytes) println("db connected, tables=" + conn.tableOperations.list) {code} > accumulo client tries to connect only to the first ZK in the list, making it SPOF > --------------------------------------------------------------------------------- > > Key: ACCUMULO-3485 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3485 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.6.1 > Reporter: Denis Petrov > Priority: Critical > > Accumulo client tries to connect only to the first ZK server. > if that single ZK server is down, the accumulo client does not try other ZK servers. > Thus the first ZK is single point of failure, if it is down, accumulo client cannot work > {code:java} > val instance = new ZooKeeperInstance("zzz", "no-zk-here.example.com,zk1.example.com,zk2.example.com,zk3.example.com") > val conn = instance.getConnector("root", "pass".getBytes) > println("db connected, tables=" + conn.tableOperations.list) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)