I'm afraid I don't understand. You're saying that optimising is causing performance issues?
Simple solution: DO NOT OPTIMIZE! Optimisation is very badly named. What it does is squashes all segments in your index into one segment, removing all deleted documents. It is good to get rid of deletes - in that sense the index is "optimized". However, future merges become very expensive. The best way to handle this topic is to leave it to Lucene/Solr to do it for you. Pretend the "optimize" option never existed. This is, of course, assuming you are using something like Solr 3.5+. Upayavira On Mon, Jun 29, 2015, at 08:08 AM, Summer Shire wrote: > > Have to cause of performance issues. > Just want to know if there is a way to tap into the status. > > > On Jun 28, 2015, at 11:37 PM, Upayavira <u...@odoko.co.uk> wrote: > > > > 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 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 optimize is happening is returning OK because > >> technically > >> solr allows you to update when an optimize is happening. > >> > >> any suggestions ? > >> > >> thanks, > >> Summer
