From user-return-11406-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Tue May 1 21:52:25 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 64F35180645 for ; Tue, 1 May 2018 21:52:25 +0200 (CEST) Received: (qmail 51111 invoked by uid 500); 1 May 2018 19:52:23 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 51095 invoked by uid 99); 1 May 2018 19:52:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2018 19:52:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id ADDD41A1FFD for ; Tue, 1 May 2018 19:52:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.112 X-Spam-Level: X-Spam-Status: No, score=-0.112 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=elyograg.org Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id BXmmUfOKNJ2n for ; Tue, 1 May 2018 19:52:21 +0000 (UTC) Received: from frodo.elyograg.org (frodo.elyograg.org [166.70.79.217]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 511095F23C for ; Tue, 1 May 2018 19:52:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by frodo.elyograg.org (Postfix) with ESMTP id 19F48B20 for ; Tue, 1 May 2018 13:52:13 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elyograg.org; h= content-language:content-transfer-encoding:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=mail; t=1525204331; bh=6ogevvB/NeqcneSLWZenElJ/COx9 4r19TwuCMO0qRBc=; b=OyCj1StffpS7ES96t8exEVQQBUYaKNbyPOgkpe4JJPir 1NybYEU72n7pKlP6BCMH3m4vHzruazXVXy1l7Myoi5UAHD88jiIZ1QqUawKUKUcJ dZp1BJ6CrhxQfpTBGqmoSmHlCPATZ9fwUJnlZM07ujUCr/GsbC4/uogs75N8ZPY= X-Virus-Scanned: Debian amavisd-new at frodo.elyograg.org Received: from frodo.elyograg.org ([127.0.0.1]) by localhost (frodo.elyograg.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id HHQp+Ca2gPyB for ; Tue, 1 May 2018 13:52:11 -0600 (MDT) Received: from [10.2.0.108] (client175.mainstreamdata.com [209.63.42.175]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: elyograg@elyograg.org) by frodo.elyograg.org (Postfix) with ESMTPSA id 65B36A31 for ; Tue, 1 May 2018 13:52:08 -0600 (MDT) Subject: Re: Configuring SolrCloud with Redundancy on Two Physical Frames To: user@zookeeper.apache.org References: From: Shawn Heisey Message-ID: <9310f9bf-6273-bc0e-662b-97fa24092d3e@elyograg.org> Date: Tue, 1 May 2018 13:52:02 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US On 5/1/2018 8:55 AM, Adam Blank wrote: > I would like to have a high-availability/redundant installation of > Zookeeper running in my production environment. The problem is that I only > have 2 physical frames available, so that rules out configuring a Zookeeper > cluster/ensemble since I'd only have redundancy if the frame with the > minority of servers goes down. What is the best practice in this situation? > Is it possible to have a separate standalone install running on each frame > connected to the same set of SOLR nodes or to use one server as primary and > one as backup? I'm more familiar with the Solr side of the equation than the ZK side.  That said, I do know if you want bulletproof fault tolerance for ZK, you must have at least three separate physical installations. For redundancy of Solr itself in SolrCloud, you only need two hosts, but for ZK, you need three.  The minimal fault tolerant SolrCloud setup would run both Solr and ZK on two servers and a third ZK by itself.  That third server would not need much horsepower.  I've heard of people using a laptop or a low-end desktop for the third server. For best results, you would also want redundancy beyond the servers themselves -- power and network for each server ideally would be separate hardware.  Some even go as far as separate racks and/or geographically diverse datacenters. Thanks, Shawn