thanks Shalin. One more question: is there any way to avoid multiple cores replicating at the same time? Like synchronizing the ReplicationHandler somehow?
On Fri, Jun 24, 2011 at 6:55 AM, Shalin Shekhar Mangar <shalinman...@gmail.com> wrote: > On Fri, Jun 24, 2011 at 1:41 PM, Esteban Donato > <esteban.don...@gmail.com> wrote: >> I have a Solr with 7 cores (~150MB each). All cores replicate at the >> same time from a Solr master instance. Every time the replication >> happens I get an OOM after experiencing long response times. This >> Solr used to have 4 cores before and I've never got an OOM with that >> configuration (replication occurs on daily basis). >> >> My question is: could the new 3 cores be the cause of OOM? Does Solr >> require considerable extra heap for performing the replication?. > > Yes and no. Replication itself does not consume a lot of heap (I guess > about a couple of MBs per ongoing replication). However, when the > searchers are re-opened on the newly installed index, auto warming can > cause memory usage to double for a core. > >> Should I avoid replicating all the cores at the same time? > > You should try that especially if you are so constrained for heap space. > >> I'm using Solr 1.4 with the following mem configuration: -Xms512m >> -Xmx512m -XX:NewSize=128M -XX:MaxNewSize=128M > > That seems to be a small amount of RAM for indexing/querying seven > 150MB indexes in parallel. > > -- > Regards, > Shalin Shekhar Mangar. >
