How big is your request size from client to server? I ran into OOM problems too. For me the reason was that I was sending big requests (10000+ docs) at too fast a pace.
So I put a throttle on the client to control the throughput of the request it sends to the server, and that got rid of the OOM error. Rebecca Tang Applications Developer, UCSF CKM Legacy Tobacco Document Library <legacy.library.ucsf.edu/> E: rebecca.t...@ucsf.edu On 6/25/14 1:45 AM, "adfel70" <adfe...@gmail.com> wrote: >I made two tests, one with MaxRamBuffer=128 and the second with >MaxRamBuffer=256. >In both i got OOM. > >I also made two tests on autocommit: >one with commit every 5 min, and the second with commit every 100,000 >docs. >(disabled softcommit) >In both i got OOM. > >merge policy - Tiered (max segment size of 5000, and merged at once = 2, >merge factor = 12). > >any idea for more tests? > > > >-- >View this message in context: >http://lucene.472066.n3.nabble.com/OOM-during-indexing-nested-docs-tp41437 >22p4143966.html >Sent from the Solr - User mailing list archive at Nabble.com.
