I think it's best to tweak merge parameters instead and amortize the cost of keeping down the number of segments. Deletes will be naturally expunged as documents come in and segments are merged. For 90% of use cases, this is the best way to go IMO. Even if you just want to get rid of deletes, look into expunge deletes - it merges just what's needed to get rid of deletes, which may not always mean a full optimize down to one segment.
My advice on optimize would be to do it when you are not going to get any updates in very often or for a long time. Otherwise it's best just to tune merge parameters and avoid optimize altogether. It's usually pre optimization that leads to the over use of optimize and it's usually unnecessary and quite costly. - Mark On Feb 18, 2013, at 11:12 AM, adm1n <evgeni.evg...@gmail.com> wrote: > Thanks for your response. > > No, nothing else. Only those errors. > > By the way, what is the best practice for optimization process - should it > be done each period of time (for example cron-based) or it depends on diff > between max doc and num docs counts? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Errors-during-index-optimization-on-solrcloud-tp4041135p4041157.html > Sent from the Solr - User mailing list archive at Nabble.com.
