Re: DirectSolrConnection, write.lock and Too Many Open Files

On 11/09/2007, at 9:48 AM, Ryan McKinley wrote: try: ulimit -n ulimit on its own is something else. On my machine I get: [EMAIL PROTECTED]:~$ ulimit unlimited [EMAIL PROTECTED]:~$ cat /proc/sys/fs/file-max 364770 [EMAIL PROTECTED]:~$ ulimit -n 1024 I have to run: ulimit -n 2 to get luce

Re: DirectSolrConnection, write.lock and Too Many Open Files

I've done a bit of poking on the server and ulimit doesn't seem to be the problem: e2wiki:~$ ulimit unlimited e2wiki:~$ cat /proc/sys/fs/file-max 170355 try: ulimit -n ulimit on its own is something else. On my machine I get: [EMAIL PROTECTED]:~$ ulimit unlimited [EMAIL PROTECTED]:~$ cat /

Re: DirectSolrConnection, write.lock and Too Many Open Files

On 11/09/2007, at 8:46 AM, Ryan McKinley wrote: lucene opens a lot of files. It can easily get beyond 1024. (I think the default). I'm no expert on how the file handling works, but I think more files are open if you are searching and writing at the same time. If you can't increase the li

Re: DirectSolrConnection, write.lock and Too Many Open Files

Adrian Sutton wrote: On 11/09/2007, at 7:21 AM, Ryan McKinley wrote: The other problem is that after some time we get a "Too Many Open Files" error when autocommit fires. Have you checked your ulimit settings? http://wiki.apache.org/lucene-java/LuceneFAQ#head-48921635adf2c968f7936dc07d51dfb4

Re: DirectSolrConnection, write.lock and Too Many Open Files

On 11/09/2007, at 7:21 AM, Ryan McKinley wrote: The other problem is that after some time we get a "Too Many Open Files" error when autocommit fires. Have you checked your ulimit settings? http://wiki.apache.org/lucene-java/ LuceneFAQ#head-48921635adf2c968f7936dc07d51dfb40d638b82 ulimit -

Re: DirectSolrConnection, write.lock and Too Many Open Files

The other problem is that after some time we get a "Too Many Open Files" error when autocommit fires. Have you checked your ulimit settings? http://wiki.apache.org/lucene-java/LuceneFAQ#head-48921635adf2c968f7936dc07d51dfb40d638b82 ulimit -n . As mike mentioned, you may also want to use 's

Re: DirectSolrConnection, write.lock and Too Many Open Files

On Sep 10, 2007, at 5:00 PM, Mike Klaas wrote: On 10-Sep-07, at 1:50 PM, Adrian Sutton wrote: We use DirectSolrConnection via JNI in a couple of client apps that sometimes have 100s of thousands of new docs as fast as Solr will have them. It would crash relentlessly if I didn't force all

Re: DirectSolrConnection, write.lock and Too Many Open Files

On 10-Sep-07, at 1:50 PM, Adrian Sutton wrote: We use DirectSolrConnection via JNI in a couple of client apps that sometimes have 100s of thousands of new docs as fast as Solr will have them. It would crash relentlessly if I didn't force all calls to update or query to be on the same thread

Re: DirectSolrConnection, write.lock and Too Many Open Files

On 9/10/07, Adrian Sutton <[EMAIL PROTECTED]> wrote: > Can Solr as a web app handle multiple updates at > once or does it synchronize to avoid it? Yep... things aren't synchronized at the top level and are designed to be thread-safe. -Yonik

Re: DirectSolrConnection, write.lock and Too Many Open Files

We use DirectSolrConnection via JNI in a couple of client apps that sometimes have 100s of thousands of new docs as fast as Solr will have them. It would crash relentlessly if I didn't force all calls to update or query to be on the same thread using objc's @synchronized and a message queue

Re: DirectSolrConnection, write.lock and Too Many Open Files

On Sep 10, 2007, at 1:33 AM, Adrian Sutton wrote: After a while we start getting exceptions thrown because of a timeout in acquiring write.lock. It's quite possible that this occurs whenever two updates are attempted at the same time - is DirectSolrConnection intended to be thread safe?