Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (nike.apache.org: domain of mutsuzaki@gmail.com designates
 209.85.220.173 as permitted sender)
MIME-Version: 1.0
Reply-To: michi@cs.stanford.edu
Sender: mutsuzaki@gmail.com
In-Reply-To: 
 <CAH-BiJi5fDm16w+DRUk5XzbxtiwD0S8MQj_otm_O+sH3gLfQcQ@mail.gmail.com>
References: 
 <CAH-BiJi5fDm16w+DRUk5XzbxtiwD0S8MQj_otm_O+sH3gLfQcQ@mail.gmail.com>
Date: Wed, 19 Mar 2014 23:14:00 -0700
Message-ID: 
 <CAHYqJpGBE+X5PQUaWn1U1MF=unKEW=eDG31M-d_8yfP=A4-oxA@mail.gmail.com>
Subject: Re: Best pratice
From: Michi Mutsuzaki <michi@cs.stanford.edu>
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

It should be fine to consolidate so long as these applications don't
overload the ZooKeeper cluster in terms of memory usage and read/write
throughput. I would definitely test it first though :)

On Wed, Mar 19, 2014 at 9:57 PM, Software Dev <static.void.dev@gmail.com> wrote:
> We currently have 4 separate ZK clusters (hbase, kafka, solr cloud, storm)
> with either 3 or 5 per cluster. Should we combine all clusters into one and
> just serve each one up in their own chroot?