Hi All,
I have two indexers (Independent processes ) writing to a common solr core.
If One indexer process issued an optimize on the core
I want the second indexer to wait adding docs until the optimize has finished.
Are there ways I can do this programmatically?
pinging the core when the optimi
Hi Erick,
Yes CloudSolrClient is better suited for cloud environments, in this case I'm
dealing with a single server with multiple collections. In the code I provide
the ability to switch to CloudSolrClient instead of CUSC if a zookeper URL is
specified, so for now this must work for cloud and
Ups, sorry I forgot the issue URL:
https://issues.apache.org/jira/browse/SOLR-7729
- Original Message -
From: "Erick Erickson"
To: solr-user@lucene.apache.org
Sent: Saturday, June 27, 2015 11:33:53 AM
Subject: [MASSMAIL] Re: ConcurrentUpdateSolrClient ignoring the collection
param in so
On 6/28/2015 2:59 PM, Jorge Luis Betancourt González wrote:
> Yes CloudSolrClient is better suited for cloud environments, in this case I'm
> dealing with a single server with multiple collections. In the code I provide
> the ability to switch to CloudSolrClient instead of CUSC if a zookeper URL
Hi All,
I have two indexers (Independent processes ) writing to a common solr core.
If One indexer process issued an optimize on the core
I want the second indexer to wait adding docs until the optimize has finished.
Are there ways I can do this programmatically?
pinging the core when the optimi
Bigger question, why are you optimizing? Since 3.6 or so, it generally
hasn't been requires, even, is a bad thing.
Upayavira
On Sun, Jun 28, 2015, at 09:37 PM, Summer Shire wrote:
> Hi All,
>
> I have two indexers (Independent processes ) writing to a common solr
> core.
> If One indexer process
