On 8/21/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: > > : I'm wondering what's the best way to completely change a big index > : without loosing any requests. > > use the snapinstaller script -- or adopt the same atomic copying approach > it uses.
I'm having a look :) > : - Between the two mv's, the directory dir does not exists, which can > : cause some solr failure. > > this shouldn't cause any failure unless you tell Solr to try and reload > turing the move (ie: you send it a commit) ... either way an atomic copy > in place of a mv should work much better. Why, does the reloading of the searcher triggers a re loading of the files from disk ? Thx ! > > -Hoss > > -- Jerome Eteve. [EMAIL PROTECTED] http://jerome.eteve.free.fr/
