Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-13 Thread Michael McCandless
Lucene (or actually Lucene + > Compass), not Zoie at the moment.  For some of the responses, I'm not clear > if the information applies to Zoie specifically, or also to straight Lucene. > -- > View this message in context: > http://old.nabble.com/Lucene-2.9.0-Near-Real-Tim

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-13 Thread Michael McCandless
>> merges them together to feed to one Zoie instance, then a broker on top of >> zoie which serves out IndexReaders to different applications living on top >> which can wrap them up in their own business logic as they saw fit... as >> long as it was ok to have all the applications

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-13 Thread jchang
d updates in a crash? BTW, I'm using straight Lucene (or actually Lucene + Compass), not Zoie at the moment. For some of the responses, I'm not clear if the information applies to Zoie specifically, or also to straight Lucene. -- View this message in context: http://old.nabble.com/L

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-13 Thread jchang
iving on top > which can wrap them up in their own business logic as they saw fit... as > long as it was ok to have all the applications in the same JVM, of > course). > > -jake > > >> >> Otis >> -- >> Sematext -- http://sematext.com/ -- Solr - Lucene -

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-13 Thread Michael McCandless
On Wed, Jan 13, 2010 at 7:33 AM, John Wang wrote: > "NRT reader "simply" lets you search the full index, including > un-committed changes." > > I am not sure I understand: > > I think the context of the discussion is for when the indexer crashes before > IW.commit. At which point, does not really

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-13 Thread John Wang
"NRT reader "simply" lets you search the full index, including un-committed changes." I am not sure I understand: I think the context of the discussion is for when the indexer crashes before IW.commit. At which point, does not really matter if you are using NRT, e.g. IW.getReader, or IndexReader.

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-13 Thread Michael McCandless
On Tue, Jan 12, 2010 at 6:10 PM, jchang wrote: > Does anybody know how this works out with service restarts (both orderly > shutdown and a crash)?  If the service goes down while indexed items are in > RAMDir but not on disk, are they lost?  Or is there some kind of log > recovery? Lucene expose

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread Jake Mannix
On Tue, Jan 12, 2010 at 10:14 PM, Jason Rutherglen < jason.rutherg...@gmail.com> wrote: > Jake, > > I wonder how often people need reliable transactions for > realtime search? Maybe Mysql's t-log could be used sans the > database part? > A reliable message queue - I'd imagine all the time! Trans

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread Jason Rutherglen
ons) and also have applications not involved in the writing >> > also >> > seeing (in real-time) these writes, then you could still do it with >> > Zoie, >> > but it would take some interesting architectural juggling (write your >> > own >> > StreamDataProvider class which ta

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread Jake Mannix
> Does anybody know how this works out with service restarts (both > orderly > >> > shutdown and a crash)? If the service goes down while indexed items > are > >> > in > >> > RAMDir but not

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread Jason Rutherglen
this which clustered lucene servers? >> If you have numerous servers running off one index, I assume there is no way >> for the other services to pick up the newly indexed items until they are >> flushed to disk, correct?  I'd be happy if that is not so, but I suspect it >>

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread Jason Rutherglen
hich serves out IndexReaders to different applications living on top > which can wrap them up in their own business logic as they saw fit... as > long as it was ok to have all the applications in the same JVM, of course). >   -jake > >> >>  Otis >> -- >> Sematext -- http://sem

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread Jake Mannix
log > > recovery? > > > > Also, does anybody know the impact of this which clustered lucene > servers? > > If you have numerous servers running off one index, I assume there is no > way > > for the other services to pick up the newly indexed items until the

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread Otis Gospodnetic
.apache.org > Sent: Tue, January 12, 2010 6:10:56 PM > Subject: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts > > > Lucene 2.9.0 has near real time indexing, writing to a RAMDir which gets > flushed to disk when you do a search. > > Does anybody k

Re: Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread Jason Rutherglen
gt; is so. > > Thanks, > John > -- > View this message in context: > http://old.nabble.com/Lucene-2.9.0-Near-Real-Time-Indexing-and-Service-Crashes-restarts-tp27136539p27136539.html > Sent from the Lucene - Java Developer mailing list archive at Nabble.com. > > > --

Lucene 2.9.0 Near Real Time Indexing and Service Crashes/restarts

2010-01-12 Thread jchang
x27;d be happy if that is not so, but I suspect it is so. Thanks, John -- View this message in context: http://old.nabble.com/Lucene-2.9.0-Near-Real-Time-Indexing-and-Service-Crashes-restarts-tp27136539p27136539.html Sent from the Lucene - Java Developer mailing list archive at Nabbl