lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: cores vs. instances vs. zookeeper vs. cloud vs ?
Date Fri, 16 Dec 2016 16:38:47 GMT
It's not quite clear to me whether you're using SolrCloud now or not, my
guess is not. My guess here is that you _should_ move to SolrCloud and
collections. Then, instead of thinking about "cores", you just think about
collections. Where the replicas live then isn't something you have to manage
in that case.

There's a bit of a learning curve for Zookeeper, and a mental shift you
have to make to not worry about cores at all, just trust Solr. That said,
if you _want_ to explicitly manage where each and every core for each
and every collection lives, that's easy with the collections API. Once you
do make that shift, going back is painful ;)

So the scenario is that you have three collections, prod, dev, demo. They all
happen to use the same configset (which you keep in ZK). You have one
zookeeper ensemble that the three collections reference. They can even
all share the same machine if that machine has sufficient capacity.

The deal here is that these are really completely independent; you'll have
to index your content to each separately.

But then your URL becomes x.x.x.x:8983/solr/prod, x.x.x.x:8983/solr/dev
and the like.

FWIW,
Erick

On Fri, Dec 16, 2016 at 5:26 AM, John Blythe <john@curvolabs.com> wrote:
> good morning everyone.
>
> i've got a crowing number of cores that various parts of our application
> are relying upon. i'm having difficulty figuring out the best way to
> continue expanding for both sake of scale and convenience.
>
> i need two extra versions of each core due to our demo instance and our
> development instance. when we had just one or two cores it wasn't the worst
> thing to have cores like X, demo-X, and dev-X. that has quickly become
> unnecessarily cumbersome.
>
> i've considered moving each instance to its own solr instance, perhaps just
> throwing it on a different port. for example, production could be
> x.x.x.x:8983, dev x.x.x.x:8993, and demo x.x.x.x:8938.
>
> i'm pretty helpless at this point with zookeeper and/or solrcloud. given
> the above info, i'd love to hear some quick overview ideas as to the best
> approach that i can then begin to explore online.
>
> thanks for any pointers!

Mime
View raw message