[KinoSearch] KinoSearch Death

Chris Nandor projects at pudge.net
Wed Oct 25 09:48:35 PDT 2006


At 9:18 -0700 2006.10.25, Marvin Humphrey wrote:
>Yes, right again.  The problem would occur more rarely without
>caching, but it can still happen if you create a Searcher and an
>indexer deletes files out from underneath it before the search and
>all related actions finish up.  Basically, you can never update a
>live index on NFS 100% safely, either via an InvIndexer, or by
>copying a new index on top of the old.  You have to maintain multiple
>copies and switch your Searchers over to using the new one before
>modifying the old.

But then you end up with stale index files, unless you have some way to
prune them later.  I suppose it's worth asking: is there a way to know
which files are no longer in use in a given invindex directory, and maybe
for how long they have been OUT of use?

Do you get where I am going with this?  I previously did what you
suggested, but then I ended up with almost 7000 files in my invindex
directory after several days, because I would delete old index files in one
copy of the index, but then when I copied files back to the other index ...

Also, any ETA on the next version with sorting?  :)

-- 
Chris Nandor                      pudge at pobox.com    http://pudge.net/
Open Source Technology Group       pudge at ostg.com     http://ostg.com/



More information about the kinosearch mailing list