Hi,
My problem is more: If you want to start a single Solr server, why the
hell do you want a zookeeper? This is total crap and waste of resources
and a security leak on top (why start some software that you don't need?).
I would agree with the new Solr Cloud default, if there would be by
de
Standalone makes sense for the configs. Each node has their own local set of
configs which are not shared.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Feb 28, 2024, at 10:51 AM, David Smiley wrote:
>
> On Wed, Feb 28, 2024 at 7:50 AM Gus Heck
On Wed, Feb 28, 2024 at 7:50 AM Gus Heck wrote:
> IIRC "standalone" was deemed the wrong color for the shed because
> [original/non-cloud/standalone/legacy/user-managed] solr can have more than
> one machine, and does distributed search.
Nonetheless each node acts alone and/or acts on requests wh
This change is definitely NOT about requiring them to use Solr Cloud….
We’ve changed the bin/solr script to require a “start” parameter, so “bin/solr
start” to fire up solr, so if you are used to "bin/solr", you will need to
learn the “bin/solr start” command. Though, if you are using install
Please no :-) 100% of my small/medium sized customers would never ever
use Solr Cloud.
Uwe
Am 23.02.2024 um 19:06 schrieb Eric Pugh:
During today’s community discussion the topic of moving to defaulting to
SolrCloud mode came up.
The idea here is that when a user run’s “bin/solr start” it fi
IIRC "standalone" was deemed the wrong color for the shed because
[original/non-cloud/standalone/legacy/user-managed] solr can have more than
one machine, and does distributed search.
On Mon, Feb 26, 2024 at 3:22 PM Eric Pugh
wrote:
> Thanks for the link…. I don’t think anything I read in the
