Re: concurrent optimize and update

2008-08-13 Thread Jeremy Hinegardner
On Tue, Aug 12, 2008 at 11:51:12AM -0400, Yonik Seeley wrote: On Tue, Aug 12, 2008 at 11:19 AM, Jason Rennie [EMAIL PROTECTED] wrote: On Mon, Aug 11, 2008 at 6:41 PM, Yonik Seeley [EMAIL PROTECTED] wrote: It's safe... the adds will block until the commit or optimize has finished. By

Re: concurrent optimize and update

2008-08-12 Thread Jason Rennie
On Mon, Aug 11, 2008 at 6:41 PM, Yonik Seeley [EMAIL PROTECTED] wrote: It's safe... the adds will block until the commit or optimize has finished. By block, do you mean that the update connection(s) will be held open? Our optimizes take many minutes to complete. I'm thinking that this could

Re: concurrent optimize and update

2008-08-12 Thread Yonik Seeley
On Tue, Aug 12, 2008 at 11:19 AM, Jason Rennie [EMAIL PROTECTED] wrote: On Mon, Aug 11, 2008 at 6:41 PM, Yonik Seeley [EMAIL PROTECTED] wrote: It's safe... the adds will block until the commit or optimize has finished. By block, do you mean that the update connection(s) will be held open?

concurrent optimize and update

2008-08-11 Thread Jeremy Hinegardner
Hi all, What happens internally in solr when an optimize/commit request is submitted by one process, and some other process starts submitting Xml documents to add? Is this generally a safe thing to do? Basically I'm continually adding documents to solr, and decided that autocommit / would be

Re: concurrent optimize and update

2008-08-11 Thread Yonik Seeley
On Mon, Aug 11, 2008 at 6:16 PM, Jeremy Hinegardner [EMAIL PROTECTED] wrote: What happens internally in solr when an optimize/commit request is submitted by one process, and some other process starts submitting Xml documents to add? Is this generally a safe thing to do? It's safe... the