Does SOLR cloud push indexing across all nodes?  I've been planning 4 SOLR
boxes with only 3 exposed via the load balancer, leaving the 4th available
internally for my microservices to hit with indexing work.

I was assuming that if I hit my "solr4" IP address, only "solr4" will do
the indexing...  Perhaps I'm making a dangerous assumption?
On Apr 4, 2016 3:49 PM, "Anshum Gupta" <ans...@anshumgupta.net> wrote:

The short answer is - There's no real limit on Solr in terms of
concurrency.

Here are a few things that would impact your numbers though:
* What version of Solr are you using and how ? i.e. SolrCloud, standalone,
traditional replication ?
* Do you use atomic updates?
* How do you index ?

Assuming you are on SolrCloud, you wouldn't be able to have a dedicated
indexing node.

There are a ton of other settings you could read about and tweak to get
good throughput but in general, multi-threading is highly recommended in
terms of indexing.


On Mon, Apr 4, 2016 at 2:33 PM, Robert Brown <r...@intelcompute.com> wrote:

> Hi,
>
> Does Solr have any sort of limit when attempting multiple updates, from
> separate clients?
>
> Are there any safe thresholds one should try to stay within?
>
> I have an index of around 60m documents that gets updated at key points
> during the day from ~200 downloaded files - I'd like to fork off multiple
> processes to deal with the incoming data to get it into Solr quicker.
>
> Thanks,
> Rob
>
>
>


--
Anshum Gupta

Reply via email to