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!
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
withou
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 be
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
d
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
