Thanks Shawn, Amey, Any specific configuration needed for CloudSolrServer as I've seen increased latency on using it. Does ConcurrentUpdateSolrServer itself do discovery like CloudSolrServer.
On Mon, Oct 13, 2014 at 7:53 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 10/13/2014 5:28 AM, Apoorva Gaurav wrote: > > Is it preferable to use CloudSolrServer or using an external load > balancer > > like haproxy. We're currently channeling all our requests via haproxy but > > want to get rid of management hassles as well as additional network call > > but saw a significant degradation in latency on switching to > > CloudSolrServer. Please suggest. > > If your client is Java, then there's no contest. Use CloudSolrServer. > It can react almost instantly to cluster changes. A load balancer will > need to do a health-check cycle before it knows about machines coming up > or going down. > > The other reply that you received mentioned ConcurrentUpdateSolrServer. > This is a high-performance option, but it comes at a cost -- your > application will never be informed about any indexing errors. Even if > the index requests all fail, your application will never know. > > Thanks, > Shawn > > -- Thanks & Regards, Apoorva
