Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 33114200D0B for ; Wed, 27 Sep 2017 20:13:39 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 319911609CA; Wed, 27 Sep 2017 18:13:39 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 777B91609C1 for ; Wed, 27 Sep 2017 20:13:38 +0200 (CEST) Received: (qmail 76189 invoked by uid 500); 27 Sep 2017 18:13:37 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 76178 invoked by uid 99); 27 Sep 2017 18:13:37 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Sep 2017 18:13:37 +0000 Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 1ADB81A0044 for ; Wed, 27 Sep 2017 18:13:35 +0000 (UTC) Received: by mail-wm0-f43.google.com with SMTP id m127so21379565wmm.3 for ; Wed, 27 Sep 2017 11:13:35 -0700 (PDT) X-Gm-Message-State: AHPjjUhgFFakG39A93/h15nJQf0CRWAeZAnDrEWz7O2JsCATs8RfOwgC DwrP9KfTC/Xdz/xNlrNQwgMRdVf5PZ/ubfvNYC0= X-Google-Smtp-Source: AOwi7QBQwH2U0uAheu6mD9nMAe1NbrTclSYXwlBqDg1CRzkTuF3Vvu3vTI46rOU3HM3HCJ7KxSnR04RhJllNb/hhHvM= X-Received: by 10.28.69.11 with SMTP id s11mr905473wma.81.1506536014222; Wed, 27 Sep 2017 11:13:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.6.203 with HTTP; Wed, 27 Sep 2017 11:12:52 -0700 (PDT) In-Reply-To: References: From: Patrick Hunt Date: Wed, 27 Sep 2017 11:12:52 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: separate zookeeper client tools from server To: DevZooKeeper Content-Type: multipart/alternative; boundary="94eb2c07280cf81d0f055a2fbf8c" archived-at: Wed, 27 Sep 2017 18:13:39 -0000 --94eb2c07280cf81d0f055a2fbf8c Content-Type: text/plain; charset="UTF-8" On Fri, Sep 15, 2017 at 12:25 AM, Nicolas Franck wrote: > Hi there, > > Zookeeper is now delivered as one download, containing both the server and > the client tools. > So all yum/debian packages do the same. > > I created a zookeeper ensemble, with a zookeeper instance on each host. > From one managing server I want to send znodes to all of the zookeeper > instances. > > But in order to do that, I need to install ... zookeeper on that managing > server. > Wouldn't it be better to split both packages into a server part and a > client part? > > I suspect the main/original reason is that ZK install was pretty small, as such there was never a strong demand to split them. Additionally things like the command line shell use the client API. Most administrators want to have the client available on server machines. That said the opposite is probably not true (you typically don't need the server code on clients). Patrick > I know there is a java and a c client api, but I don't see any reason to > write code > if the tools are complete enough. > > Is this correct? How do you people do this? > > > > Thanks in advance, > > Nicolas Franck > > --94eb2c07280cf81d0f055a2fbf8c--