5-7 seconds- there's the problem. If you want to have documents visible for search within that time, you want to use the trunk and "near-real-time" search. A hard commit does several hard writes to the disk (with the fsync() system call). It does not run smoothly at that rate. It is no surprise that eventually you hit a thread-locking bug.
http://www.lucidimagination.com/search/link?url=http://wiki.apache.org/solr/RealTimeGet http://www.lucidimagination.com/search/link?url=http://wiki.apache.org/solr/CommitWithin On Wed, Mar 28, 2012 at 11:08 PM, Rafal Gwizdala <rafal.gwizd...@gmail.com> wrote: > Lance, I know there are many variables that's why I'm asking where to start > and what to check. > Updates are sent every 5-7 seconds, each update contains between 1 and 50 > docs. Commit is done every time (on each update). > Currently queries aren't very frequent - about 1 query every 3-5 seconds, > but the system is going to handle much more (of course if the problem is > fixed). > The system has 2 core CPU (virtualized) and 4 GB memory (SOLR uses about > 300 MB) > > R > > On Thu, Mar 29, 2012 at 1:53 AM, Lance Norskog <goks...@gmail.com> wrote: > >> How often are updates? And when are commits? How many CPUs? How much >> query load? There are so many variables. >> >> Check the mailing list archives and Solr issues, there might be a >> similar problem already discussed. Also, attachments do not work with >> Apache mailing lists. (Well, ok, they work for direct subscribers, but >> not for indirect subscribers and archive site users.) >> >> -- >> Lance Norskog >> goks...@gmail.com >> -- Lance Norskog goks...@gmail.com
