Actually, unless IW.commit is called, all changes after the last commit will be lost (because the segment infos file will not have been written).
On Tue, Jan 12, 2010 at 3:37 PM, Jason Rutherglen <jason.rutherg...@gmail.com> wrote: > Greetin's John, > > 2.9 and 3.0 don't use a RAMDir... Deletes are held in RAM however so > on power off, those would be lost. > > Jason > > On Tue, Jan 12, 2010 at 3:10 PM, jchang <jchangkihat...@gmail.com> wrote: >> >> 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 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? >> >> 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 they are >> flushed to disk, correct? I'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 Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-dev-h...@lucene.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
