The stack trace indicates there's an issue with optimizing. How are you kicking off optimizing? Is it automatic or manual?
34G for an index with that many documents does seem excessive. Are you re-indexing the same content with the same unique key? In other words do you have a large number of deleted documents in your index? You can tell by looking at your admin page, "schema browser" link and see if MaxDoc and NumDocs are wildly different. Is there any chance that more than one process is writing to your index? Best Erick On Tue, Mar 15, 2011 at 8:02 AM, Isha Garg <isha.g...@orkash.com> wrote: > On Tuesday 15 March 2011 01:31 PM, Anurag wrote: >> >> Do you mean that earlier it was doing indexing well then all of sudden you >> started getting this exception? >> >> ----- >> Kumar Anurag >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/background-merge-hit-exception-tp2680625p2680979.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > > ya earlier it was fine but i think as index size grows the problem start > occuring. > also I have a doubt related to index size . Isnt it is too large as > compared to no. of documents? >
