You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Dave Seltzer <ds...@tveyes.com> on 2016/12/27 15:27:10 UTC
Cloud Behavior when using
Hi Everyone,
I have a Solr index which is quite small (400,000 documents totaling 157
MB) with a query load which is quite large. I therefore want to spread the
load across multiple Solr servers.
To accomplish this I've created a Solr Cloud cluster with two collections.
The collections are configured with only 1 shard, but with 3 replicas in
order to make sure that each of the three Solr servers has all of the data
and can therefore answer any query without having to request data from
another server. I use the following command:
I use HAProxy to spread the load across the three servers by directing the
query to the server with the fewest current connections.
However, when I turn up the load during testing I'm seeing some stuff in
the logs of SERVER1 which makes me question my understanding of Solr Cloud:
SERVER1: HttpSolrCall null:org.apache.solr.common.SolrException: Error
trying to proxy request for url:
http://SERVER3:8983/solr/sf_fingerprints/select
I'm curious why SERVER1 would be proxying requests to SERVER3 in a
situation where the sf_fingerprints index is completely present on the
local system.
Is this a situation where I should be using generic replication rather than
Cloud?
Dave Seltzer <ds...@tveyes.com>
Chief Systems Architect
TVEyes
(203) 254-3600 x222