1. I never saw the poll.

2. It looks better than the previous poll, which was poorly worded. I couldn’t 
answer “yes” or “no”, really.

Here is what we have in production.

Solr 3: Using every threat I can think of to get the remaining clients off of 
it. It has been shut down in test for months.

Solr 4 master/slave: Main cluster for smallish (under 1Mdoc) collections with 
daily updates, plus one that needs to move to…

Solr 6 cloud: Hosts one small collection with strong freshness requirements and 
one large collection with very difficult queries. The second is mid-transition 
from the Solr 4 cluster.

There is no reason to go to Solr Cloud for a moderate size collection with 
daily update. None. The loose coupling makes scaling out trivial, just spin up 
an exact duplicate of an existing slave. No ADDREPLICA commands or trying to 
understand how core names are mapped to node names and then to host names 
(drives me nuts). Same thing for scaling back, take it out of the load balancer 
and shoot it.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)


> On Apr 25, 2017, at 9:23 AM, Erick Erickson <erickerick...@gmail.com> wrote:
> 
> Maybe the other thing in play here is that use-cases that "just work"
> in the master/slave environment are less likely to employ consultants
> so we get something of a skewed sense of who uses what ;)
> 
> On Tue, Apr 25, 2017 at 1:50 AM, Charlie Hull <char...@flax.co.uk> wrote:
>> On 24/04/2017 15:58, Otis Gospodnetić wrote:
>>> 
>>> Hi,
>>> 
>>> I'm really really surprised here.  Back in 2013 we did a poll to see how
>>> people were running Master-Slave (4.x back then) and SolrCloud was a bit
>>> more popular than Master-Slave:
>>> https://sematext.com/blog/2013/02/25/poll-solr-cloud-or-not/
>>> 
>>> Here is a fresh new poll with pretty much the same question - How do you
>>> run your Solr? <https://twitter.com/sematext/status/854927627748036608> -
>>> and guess what?  SolrCloud is *not* at all a lot more prevalent than
>>> Master-Slave.
>>> 
>>> We definitely see a lot more SolrCloud used by Sematext Solr
>>> consulting/support customers, so I'm a bit surprised by the results of
>>> this
>>> poll so far.
>> 
>> 
>> I'm not particularly surprised. We regularly see clients either with single
>> nodes or elderly versions of Solr (or even Lucene). Zookeeper is still seen
>> as a bit of a black art. Once you move from 'how do I run a search engine'
>> to 'how do I manage a cluster of servers with scaling for
>> performance/resilience/failover' you're looking at a completely new set of
>> skills and challenges, which I think puts many people off.
>> 
>> Charlie
>>> 
>>> 
>>> Is anyone else surprised by this?  See https://twitter.com/sematext/
>>> status/854927627748036608
>>> 
>>> Thanks,
>>> Otis
>>> --
>>> Monitoring - Log Management - Alerting - Anomaly Detection
>>> Solr & Elasticsearch Consulting Support Training - http://sematext.com/
>>> 
>>> 
>>> ---
>>> This email has been checked for viruses by AVG.
>>> http://www.avg.com
>>> 
>> 
>> 
>> --
>> Charlie Hull
>> Flax - Open Source Enterprise Search
>> 
>> tel/fax: +44 (0)8700 118334
>> mobile:  +44 (0)7767 825828
>> web: www.flax.co.uk

Reply via email to