You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by John Blythe <jo...@gmail.com> on 2018/08/23 00:23:46 UTC
Local development and SolrCloud
For those of you who are developing applications with solr and are using
solrcloud in production: what are you doing locally? Cloud seems
unnecessary locally besides testing strictly for cloud specific use cases
or configurations. Am I totally off basis there? We are considering keeping
a “standard” (read: non-cloud) local solr environment locally for our
development workflow and using cloud only for our remote environments.
Curious to know how wise or stupid that play would be.
Thanks for any info!
--
John Blythe
Re: Local development and SolrCloud
Posted by Sameer Maggon <sa...@searchstax.com>.
Why not just revert to everything SolrCloud? The advantages you will have
is that you or your other team members are using the same APIs, parameters,
experience, etc. that they will be using when they go from one environment
to another. It would be less confusion to explain to someone why you are
doing one thing in one environment and another in another. It does not seem
like there is an overhead if you used SolrCloud in your lower environments
or locally too.
You don't have to run a cluster within your local environment, you can
still have a single node "acting" as SolrCloud.
Maybe I am missing something, but what advantages or benefit you get for
*not* using SolrCloud locally?
--
Sameer Maggon
https://www.searchstax.com
On Wed, Aug 22, 2018 at 5:23 PM, John Blythe <jo...@gmail.com> wrote:
> For those of you who are developing applications with solr and are using
> solrcloud in production: what are you doing locally? Cloud seems
> unnecessary locally besides testing strictly for cloud specific use cases
> or configurations. Am I totally off basis there? We are considering keeping
> a “standard” (read: non-cloud) local solr environment locally for our
> development workflow and using cloud only for our remote environments.
> Curious to know how wise or stupid that play would be.
>
> Thanks for any info!
> --
> John Blythe
>
Re: Local development and SolrCloud
Posted by John Blythe <jo...@gmail.com>.
Thanks everyone. I think we forgot that cloud doesn’t have to be clustered.
That local overhead being avoided makes it a much easier pill to swallow as
far as local performance (vs. having all the extra containers running in
docker)
Will see what we can spin up and ask questions if/as they arise!
On Wed, Aug 22, 2018 at 17:41 Erick Erickson <er...@gmail.com>
wrote:
> I do quite a bit of "correctness" testing on a local stand-alone Solr,
> as Walter says, that's often easier to debug, especially when working
> through creating the proper analysis chains, do queries do what I
> expect and the like.
>
> That said, I'd never jump straight to SolrCloud implementations
> without my QA being on SolrCloud. Not only do subtle differences creep
> in, but some things simply aren't supported, e.g. group.func.
>
> And, as Sameer says, you can set up a SolrCloud environment on just
> your local laptop as many of the examples do for testing, there's
> nothing required about "the cloud" for SorlCloud, it's not even
> necessary to have separate machines.
>
> Best,
> Erick
>
> On Wed, Aug 22, 2018 at 5:34 PM, Walter Underwood <wu...@wunderwood.org>
> wrote:
> > We use Solr Cloud where we need sharding or near real time updates.
> > For non-sharded collections that are updated daily, we use master-slave.
> >
> > There are some scaling and management advantages to the loose
> > coupling in a master slave cluster. Just clone a slave instance and
> > fire it up. Also, load benchmarking is easier when indexing is on a
> > separate instance.
> >
> > In prod, we have 45 Solr hosts in four clusters.
> >
> > wunder
> > Walter Underwood
> > wunder@wunderwood.org
> > http://observer.wunderwood.org/ (my blog)
> >
> >> On Aug 22, 2018, at 5:23 PM, John Blythe <jo...@gmail.com> wrote:
> >>
> >> For those of you who are developing applications with solr and are using
> >> solrcloud in production: what are you doing locally? Cloud seems
> >> unnecessary locally besides testing strictly for cloud specific use
> cases
> >> or configurations. Am I totally off basis there? We are considering
> keeping
> >> a “standard” (read: non-cloud) local solr environment locally for our
> >> development workflow and using cloud only for our remote environments.
> >> Curious to know how wise or stupid that play would be.
> >>
> >> Thanks for any info!
> >> --
> >> John Blythe
> >
>
--
John Blythe
Re: Local development and SolrCloud
Posted by Erick Erickson <er...@gmail.com>.
I do quite a bit of "correctness" testing on a local stand-alone Solr,
as Walter says, that's often easier to debug, especially when working
through creating the proper analysis chains, do queries do what I
expect and the like.
That said, I'd never jump straight to SolrCloud implementations
without my QA being on SolrCloud. Not only do subtle differences creep
in, but some things simply aren't supported, e.g. group.func.
And, as Sameer says, you can set up a SolrCloud environment on just
your local laptop as many of the examples do for testing, there's
nothing required about "the cloud" for SorlCloud, it's not even
necessary to have separate machines.
Best,
Erick
On Wed, Aug 22, 2018 at 5:34 PM, Walter Underwood <wu...@wunderwood.org> wrote:
> We use Solr Cloud where we need sharding or near real time updates.
> For non-sharded collections that are updated daily, we use master-slave.
>
> There are some scaling and management advantages to the loose
> coupling in a master slave cluster. Just clone a slave instance and
> fire it up. Also, load benchmarking is easier when indexing is on a
> separate instance.
>
> In prod, we have 45 Solr hosts in four clusters.
>
> wunder
> Walter Underwood
> wunder@wunderwood.org
> http://observer.wunderwood.org/ (my blog)
>
>> On Aug 22, 2018, at 5:23 PM, John Blythe <jo...@gmail.com> wrote:
>>
>> For those of you who are developing applications with solr and are using
>> solrcloud in production: what are you doing locally? Cloud seems
>> unnecessary locally besides testing strictly for cloud specific use cases
>> or configurations. Am I totally off basis there? We are considering keeping
>> a “standard” (read: non-cloud) local solr environment locally for our
>> development workflow and using cloud only for our remote environments.
>> Curious to know how wise or stupid that play would be.
>>
>> Thanks for any info!
>> --
>> John Blythe
>
Re: Local development and SolrCloud
Posted by Walter Underwood <wu...@wunderwood.org>.
We use Solr Cloud where we need sharding or near real time updates.
For non-sharded collections that are updated daily, we use master-slave.
There are some scaling and management advantages to the loose
coupling in a master slave cluster. Just clone a slave instance and
fire it up. Also, load benchmarking is easier when indexing is on a
separate instance.
In prod, we have 45 Solr hosts in four clusters.
wunder
Walter Underwood
wunder@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Aug 22, 2018, at 5:23 PM, John Blythe <jo...@gmail.com> wrote:
>
> For those of you who are developing applications with solr and are using
> solrcloud in production: what are you doing locally? Cloud seems
> unnecessary locally besides testing strictly for cloud specific use cases
> or configurations. Am I totally off basis there? We are considering keeping
> a “standard” (read: non-cloud) local solr environment locally for our
> development workflow and using cloud only for our remote environments.
> Curious to know how wise or stupid that play would be.
>
> Thanks for any info!
> --
> John Blythe