First, committing after every add/delete is probably a bad idea unless you only add/delete very occasionally (as in no more often than every 5 minutes say).
Let your autocommit parameters commit for you. The problem here is that your searchers will try to autowarm every time you commit, which can lead to problems, especially if you're committing many times a second. Optimizing is even worse to do very frequently, and its benefits are much smaller than you'd think with recent code (3.x and trunk). Optimize will combine segments rather than letting merge factor do its job, so you should expect optimize to copy your entire index. You may not notice this is a problem with prototypes, but with a reasonable-sized corpus, this will become something you'll need to watch. You can also configure your spellcheckcomponent to automatically build on commit, or even optimize, see: http://wiki.apache.org/solr/SpellCheckComponent Best Erick On Wed, Dec 29, 2010 at 5:15 AM, Hasnain <hasn...@hotmail.com> wrote: > > Hi guys, > > Thankyou for the answers, now it is working properly. I have just one > concern about this approch, we are already committing after every > add/delete > operation. Can I substitude this with only optimize command? and how would > this effect our performance? > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Removing-deleted-terms-from-spellchecker-index-tp2161624p2162100.html > Sent from the Solr - User mailing list archive at Nabble.com. >
