Multiple webapps will not help you, they're still on the underlying memory. In fact, it'll make matters worse since they won't share resources.
So questions become: 1> Why do you have 10 cores? Putting 10 cores on the same machine doesn't really do much. It can make lots of sense to put 10 cores on the same machine for *indexing*, then replicate them out. But putting 10 cores on one machine in hopes of making better use of memory isn't useful. It may be useful to just go to one core. 2> Indexing, reindexing and searching on a single machine is requiring a lot from that machine. Really you should consider having a master/slave setup. 3> But assuming more hardware of any sort isn't in the cards, sure. reduce your cache sizes. Look at <ramBufferSizeMB> and make it small. 4> Consider indexing with Tika via SolrJ and only sending the finished document to Solr. Best Erick On Mon, Sep 12, 2011 at 5:42 AM, Manish Bafna <manish.bafna...@gmail.com> wrote: > Number of cache is definitely going to reduce heap usage. > > Can you run those xlsx file separately with Tika and see if you are getting > OOM issue. > > On Mon, Sep 12, 2011 at 3:09 PM, abhijit bashetti <abhijitbashe...@gmail.com >> wrote: > >> I am facing the OOM issue. >> >> OTHER than increasing the RAM , Can we chnage some other parameters to >> avoid the OOM issue. >> >> >> such as minimizing the filter cache size , document cache size etc. >> >> Can you suggest me some other option to avoid the OOM issue? >> >> >> Thanks in advance! >> >> >> Regards, >> >> Abhijit >> >
