OOV or OOM? Always best to post a full stack trace, and version of lucene, and OS.
Anyway - give your app more memory? Close searchers after use or some period of inactivity? Best long term solution is probably to merge the many small indexes into one, or a few, larger indexes and restrict queries by an indexed field identifying the index you are interested in. A cached filter can work well for that. -- Ian. On Mon, Jul 16, 2012 at 7:57 AM, 齐保元 <qibaoy...@126.com> wrote: > > Hi,buddy: > I have a problem concerning index readers:there are > many small index/searcher instances in my application which are hold by a > map.when new index request or seach request comes,I process them and return > the result.The problem is,when the number of small index becomes large,the > JVM throws OOV error:not enough native thread.So,any idea to solve this > problem? > > -- > > ____________________________________________ > 齐保元(Qi Baoyuan) > 中科院计算技术研究所 智能信息处理重点实验室(ICT,NKI,GUCAS,Beijing,China) > 手机：15120084688 > E-Mail：qibaoy...@126.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
