Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper >> mail # user >> ZK ensemble resused or dedicated?


Copy link to this message
-
Re: ZK ensemble resused or dedicated?
For production settings with well-behaved applications, sharing is not a
bad idea.  I would definitely isolate development efforts onto a dev
instance of ZK.  And if you have trigger happy admins who think rebooting
fixes all ills, I would consider separating apps.

How is it that you wound up with your problem of being unable to manipulate
one thing without changing others?
On Mon, Oct 28, 2013 at 7:20 AM, Hoggarth, Gil <[EMAIL PROTECTED]> wrote:

> Hi all,
>
>
>
> Recently I stored the configs of a new Solr service in a ZK ensemble and
> struggled because I'd made an error (numShards incorrectly set) but
> found I couldn't edit it without risking the other configs stored in the
> ZK ensemble.
>
>
>
> In general, do you recommend that a ZK ensemble is dedicated to a single
> service, or do you recommend an ensemble be used for many services? If
> the latter, what's the recommended way of correcting individual service
> issues without affecting the other existing configs in the ensemble?
>
>
>
> Thanks in advance, Gil
>
>
>
> Gil Hoggarth
>
> Web Archiving Technical Services Engineer
>
> The British Library, Boston Spa, West Yorkshire, LS23 7BQ
>
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB