Thanks Shawn. I was looking at SOLR Admin UI and also using top command on server.
Im running a endurance for 4 hr with 50/sec TPS and i see the physical memory keeps on increasing during the time and if we have schedule delta import during that time frame which can import upto 4 million docs. After the import I see again the memory increases and their comes a point when their is no more memory left which in turn leads to OOM. I have seen one more thing if their is no activity on server no import , no search going. I have not seen the memory coming down from the state which was created after test. Couple of things to notice: 1. We are storing data and indexing also. (not sure if that is causing problem). 2. Is 8 GB enuf for 10 million or more data to index. 3. We have custom handler which extend solr handlers to return data when client calls solr handler. Let me know, if we are missing configuration pieces. -- View this message in context: http://lucene.472066.n3.nabble.com/SOLR-Physical-Memory-leading-to-OOM-tp4222299p4222314.html Sent from the Solr - User mailing list archive at Nabble.com.
