lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Devin Foley <>
Subject Deadlock in Server?
Date Fri, 20 Aug 2010 18:03:54 GMT
Hi All,

I'm currently using Solr to run a search engine that is pulling in new data
24 hours a day.  Currently, I'm indexing about 5 million documents per day,
each document being around 2k in size.  Every few days, the server locks up,
and calls to /update stop working.  During this lock, CPU, memory and disk
utilization on the server shoot up.  After 30-60 minutes, the server starts
accepting updates again, without intervention on my part.  Also, during the
lock, I am still able to /select.  I just can't /update.

I viewed the thread dump in the admin panel during the last lockup, and
found a lot of these:

'btpool0-868' Id=7582, WAITING on
total cpu time=0.0000ms user time=0.0000ms
... (java.util stuff)

I'm using Solr 1.4.0, SolrJ 1.4.1 (StreamingUpdateSolrServer), and Java
1.6.0 64bit on CentOS.

My questions...

1) Has anybody else experienced this?
2) Has this been addressed in Solr 1.4.0?
3) How can I stop this from happening?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message