Ok nevermind actually - the simultaneous indexing was something done in zoie 1.3, and was changed in 1.4 to addIndexesNoOptimize() on the RAMDirectory indexes as soon as they are big enough.
It's still true that you can throw away the RAMDirectory once the disk index is reopened though. -jake On Sun, Oct 11, 2009 at 3:36 PM, Jake Mannix <jake.man...@gmail.com> wrote: > Hey Eric, > > One clarification before letting the rest of this discussion sneak over > to the zoie list: > > On Sun, Oct 11, 2009 at 1:51 PM, Angel, Eric <ean...@business.com> wrote: > > * Am I wrong to assume that the RAMDir holds the entire index - just as the >> FSDir? Or does RAMDir only hold a portion of the index that hasn't yet been >> flushed to disk? >> > > With zoie, you index to the FSDir *and* the RAMDir simultaneously (so there > is increased CPU usage for indexing because of this), but you only reopen() > the IndexReader on the FSDir every 15minutes (or so), so the fact that > you've been writing to it the whole while is invisible to the application in > the intervening time. This means that a) you don't need to worry about > disaster recovery any worse than a regular non-realtime setup, and b) that > when it's time to reopen the FSDir based index, you don't need to write the > RAMDir to disk, you can just throw it away, as the disk already has the docs > that are in that RAMDir. > > -jake >
