from doing less comparissons, simple calculations or both (which I assume
it's the case)
Thanks!
--
Fernando Otero
Sr Engineering Manager, Panamera
Buenos Aires - Argentina
Email: fernando.ot...@olx.com
he preference that
> indicates PULL replicas would keep the queries so they are running only
> on the four machines with more memory.
>
> The reason that you want two TLOG replicas instead of one is so that if
> the current leader dies, there is another TLOG replica available to
> bec
Hi guys,
I read in several blog posts that it's never a good idea to index and
search on the same node. I wonder how that can be achieved in Solr Cloud or
if it happens automatically.
--
Fernando Otero
Sr Engineering Manager, Panamera
Buenos Aires - Argentina
Mobile: +54 911 676
cal shards are queried.
>
> HTH,
> Emir
> --
> Monitoring - Log Management - Alerting - Anomaly Detection
> Solr & Elasticsearch Consulting Support Training - http://sematext.com/
>
>
>
> > On 25 Oct 2018, at 16:18, Fernando Otero wrote:
> >
> > Hey Shawn
> &g
n Tue, Oct 23, 2018 at 2:21 PM Shawn Heisey wrote:
> On 10/23/2018 9:31 AM, Fernando Otero wrote:
> > Hey all
> > I'm running some tests on Solr cloud (10 nodes, 3 shards, 3
> replicas),
> > when I run the queries I end up seeing 7x traffic ( requests / minute)
Hey all
I'm running some tests on Solr cloud (10 nodes, 3 shards, 3 replicas),
when I run the queries I end up seeing 7x traffic ( requests / minute) in
Newrelic.
Could it be that the internal communication between nodes is done through
HTTP and newrelic counts those calls?
Thanks!
