Re:OOM at solr master node while updating document

Seems FieldCache consume all the heap. At 2011-07-05 16:25:27，Chengyang atreey...@163.com wrote: Is there any memory leak when I updating the index at the master node? Here is the stack trace. o.a.solr.servlet.SolrDispatchFilter - java.lang.OutOfMemoryError: Java heap space

OOM at solr master node while updating document

Is there any memory leak when I updating the index at the master node? Here is the stack trace. o.a.solr.servlet.SolrDispatchFilter - java.lang.OutOfMemoryError: Java heap space at org.apache.solr.handler.ReplicationHandler$FileStream.write(ReplicationHandler.java:1000) at

after the slave node pull index from master, when will solr del the tmp index dir

I noticed that the slave node have some tmp Index.x dir that created during the index sync with master, but they are not removed even after serval days. So when will solr del the tmp index dir?

JVM GC is very frequent.

We have about 500million documents are indexed.The index size is aobut 10G. Running on a 32bit box. During the pressure testing, we monitered that the JVM GC is very frequent, about 5min once. Is there any tips to turning this?

In multicore env, can I make it access core0 by default

Thus when I access http://localhost/solr/select?q=*:* equals http://localhost/solr/core0/select?q=*:*.

Is there a better for solor server side loadbalance?

The default solr solution is client side loadbalance. Is there a solution provide the server side loadbalance?

Is solr able to merge index on different nodes

Once I want to create a large index, can I split the index on different nodes and the merge all the indexs to one node. Any further suggestion for this case?

Any tips/guidelines to turning the Solr/luence performance in a master/slave/sharding environment

How to reduce the index files size, decreate the sync time between each nodes. decrease the index create/update time. Thanks.

Re:Re: Any there any known issues may cause the index sync between the master/slave abnormal?

Hi Peter, Thanks your reponse. I will check the http://wiki.apache.org/solr/SolrReplication first. I mean the slave node did not delete the old index and finally cause the disk usage to large for the slave node. I am thinking to manually force the slave node to refresh the index. Regards,

Any there any known issues may cause the index sync between the master/slave abnormal?

Any there any known issues may cause the index sync between the master/slave abnormal? And is there any API to call to force sync the index between the master and slave, or force to delete the old index on the slave?