Re: DirectUpdateHandler2 threads pile up behind scheduleCommitWithin

2009-05-12 Thread jayson.minard
first wrote the multi-threaded-ness of DUH2, I'd be very happy to promptly review any improvements made to it. -Mike -- View this message in context: http://www.nabble.com/DirectUpdateHandler2-threads-pile-up-behind-scheduleCommitWithin-tp23431691p23472391.html Sent from the Solr - Dev

Re: DirectUpdateHandler2 threads pile up behind scheduleCommitWithin

2009-05-12 Thread Shalin Shekhar Mangar
On Tue, May 12, 2009 at 5:49 AM, Mike Klaas mike.kl...@gmail.com wrote: Thanks, I'll take a look in the next few days. The current patch doesn't guarantee index consistency during post-commit callback hooks, right? This could be a problem for index replication. (Incidentally, I'm rather

Re: DirectUpdateHandler2 threads pile up behind scheduleCommitWithin

2009-05-11 Thread Mike Klaas
://www.nabble.com/DirectUpdateHandler2-threads-pile-up-behind-scheduleCommitWithin-tp23431691p23472391.html Sent from the Solr - Dev mailing list archive at Nabble.com.

Re: DirectUpdateHandler2 threads pile up behind scheduleCommitWithin

2009-05-08 Thread Mike Klaas
On 7-May-09, at 10:36 AM, jayson.minard wrote: Does every thread really need to notify the update handler of the commit interval/threshold being reached, or really just the first thread that notices should send the signal, or better yet a background commit watching thread so that no

Re: DirectUpdateHandler2 threads pile up behind scheduleCommitWithin

2009-05-07 Thread jayson.minard
. That is assuming they wouldn't need to block like they are now for a reason I'm likely unaware of... --j -- View this message in context: http://www.nabble.com/DirectUpdateHandler2-threads-pile-up-behind-scheduleCommitWithin-tp23431691p23431745.html Sent from the Solr - Dev mailing list archive at Nabble.com.