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 <wun...@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 > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > >> On Aug 22, 2018, at 5:23 PM, John Blythe <johnbly...@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 >
