lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: Adding docs to solr - slows down searcher requests
Date Wed, 26 Sep 2018 17:10:07 GMT
5 zookeepers is overkill for 4 nodes. 3 should be more than adequate.
But that's a tangent.

Sure. Configs to tune:
1> indexing rate. If you're flooding the cluster with updates at a
very high rate, the CPU cycles needed to index the docs are going to
take away from query processing. So if you throttle your indexing you
can maybe make it better.

2> How often to you commit such that it opens a searcher? Either soft
commits or hard commits with openSearcher=true. See:
https://lucidworks.com/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/

3> How much autowarming are you doing? Excessive autowarm counts for
filterCache and querResult cache can be a problem, especially when
combined with frequent commits. Contrariwise, no autowarming at all
will also cause response spikes. I usually start with 10-20.

4> If you're using a 7x version of Solr, you can use TLOG and/or PULL
replicas. Those index on the leader then the updated index is pushed
to the follower.

5> If the client that sends docs is issuing a commit with every
update, that's an anti-pattern. Check that.

Best,
Erick
On Wed, Sep 26, 2018 at 9:24 AM ashoknix <ashok.nix@gmail.com> wrote:
>
> We have solr cloud  4 nodes with 5 zookeepers.
>
> Usually search request are super fast! But, when we add docs to leader solr
> - it starts pushing updates to other nodes - causing search request to
> respond back at snail speed :( :( :(
>
> We see tons of such logs for period of 2-3 mins and then once it is
> completed - again searcher is faster.
>
> 65497572 [http-apr-8980-exec-40] INFO
> org.apache.solr.update.processor.LogUpdateProcessor  – [bbc] webapp=/solr
> path=/update params=
> {distrib.from=http://ser6.rit.net:8980/solr/bbc/&update.distrib=FROMLEADER&wt=javabin&version=2&update.chain=dedupe}
> {add=[B63AD0671A5E57B9 (1612655281772167168), 00B8A4CCFABFA1AC
> (1612655281784750080), 9C89A1516C9166E6 (1612655281798381568),
> 9322E17ECEAADE66 (1612655281803624448), C6DDB4BF8E94DE6B
> (1612655281814110208), DAA49178A5E74285 (1612655281830887424),
> 829C2AE38A3E78E4 (1612655281845567488), 4C7B19756D8E4208
> (1612655281859198976), BE0F7354DC30164C (1612655281869684736),
> 59C4A764BB50B13B (1612655281880170496)]} 0 9
>
> Can SOLR gurus - advise what is the best strategy to follow ? / or any
> configs to tune ? or any other methods ?
>
> Thanks a ton!
>
>
>
>
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Mime
View raw message