On 3/25/11 11:25 AM, David McLaughlin wrote:
Thanks Chris. I dug into the SolrCore code and after reading some of the
code I ended up going with core.getNewestSearcher(true) and this fixed the
problem.
FYI, openNew=true is not implemented and can result in an
UnsupportedOperationException. For
Thanks Chris. I dug into the SolrCore code and after reading some of the
code I ended up going with core.getNewestSearcher(true) and this fixed the
problem.
David
On Thu, Mar 24, 2011 at 7:20 PM, Chris Hostetter
wrote:
> : I am not familiar with Solr internals, so the approach I wanted to take
: I am not familiar with Solr internals, so the approach I wanted to take was
: to basically check the numDocs property of the index during start-up and set
: a READABLE state in the ZooKeeper node if it's greater than 0. I also
: planned to create a commit hook for replication and updating which
:
Hi,
In our Solr deployment we have a cluster of replicated Solr cores, with the
small change that we have dynamic master look-up using ZooKeeper. The
problem I am trying to solve is to make sure that when a new Solr core joins
the cluster it isn't made available to any search services until it has
