That is an interesting point - what size of instance is needed for a
zookeeper. Can it run well in a micro?
Another issue I wanted to raise is that maybe questions, advice, and
guidelines should be relative to the "shirt size" of your cluster - small,
medium, or large. SolrCloud is clearly more optimized for medium to large
clusters. Sure, you can use it for small clusters, but then some of the
features and guidance do seem like overkill. Nonetheless, I would hate to
see anybody take the compromised guidance for very small clusters (3 or 4
machines) and apply it to even medium-size clusters (10 to 20 machines), let
alone large clusters (dozens to 100 or more machines).
-- Jack Krupansky
-----Original Message-----
From: Otis Gospodnetic
Sent: Thursday, November 22, 2012 9:37 AM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud and external Zookeeper ensemble
If your Solr instances don't max out your ec2 instances you should be fine.
But maybe even micro instances will suffice. Or 1 on demand and 2 spot
ones. If cost is the concern, that is.
Otis
--
SOLR Performance Monitoring - http://sematext.com/spm
On Nov 21, 2012 5:07 PM, "Marcin Rzewucki" <mrzewu...@gmail.com> wrote:
Yes, I meant the same (not -zkRun). However, I was asking if it is safe to
have zookeeper and solr processes running on the same node or better on
different machines?
On 21 November 2012 21:18, Rafał Kuć <r....@solr.pl> wrote:
> Hello!
>
> As I told I wouldn't use the Zookeeper that is embedded into Solr, but
> rather setup a standalone one.
>
> --
> Regards,
> Rafał Kuć
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch -
ElasticSearch
>
> > First of all: thank you for your answers. Yes, I meant side by side
> > configuration. I think the worst case for ZKs here is to loose two of
> them.
> > However, I'm going to use 4 availability zones in same region so at
least
> > this will reduce the risk of loosing both of them at the same time.
> > Regards.
>
> > On 21 November 2012 17:06, Rafał Kuć <r....@solr.pl> wrote:
>
> >> Hello!
> >>
> >> Zookeeper by itself is not demanding, but if something happens to
> >> your
> >> nodes that have Solr on it, you'll loose ZooKeeper too if you have
> >> them installed side by side. However if you will have 4 Solr nodes
> >> and
> >> 3 ZK instances you can get them running side by side.
> >>
> >> --
> >> Regards,
> >> Rafał Kuć
> >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch -
> ElasticSearch
> >>
> >> > Separate is generally nice because then you can restart Solr nodes
> >> > without consideration for ZooKeeper.
> >>
> >> > Performance-wise, I doubt it's a big deal either way.
> >>
> >> > - Mark
> >>
> >> > On Nov 21, 2012, at 8:54 AM, Marcin Rzewucki <mrzewu...@gmail.com>
> >> wrote:
> >>
> >> >> Hi,
> >> >>
> >> >> I have 4 solr collections, 2-3mn documents per collection, up to
100K
> >> >> updates per collection daily (roughly). I'm going to create
> SolrCloud4x
> >> on
> >> >> Amazon's m1.large instances (7GB mem,2x2.4GHz cpu each). The
> question is
> >> >> what about zookeeper? It's going to be external ensemble, but is
> >> >> it
> >> better
> >> >> to use same nodes as solr or dedicated micro instances? Zookeeper
> does
> >> not
> >> >> seem to be resources demanding process, but what would be better
> >> >> in
> this
> >> >> case ? To keep it inside of solrcloud or separately (micro
instances
> >> seem
> >> >> to be enough here) ?
> >> >>
> >> >> Thanks in advance.
> >> >> Regards.
> >>
> >>
>
>
