Hi Alexander, thank you for your response.
You said that the old index files were still in use. That means Linux does not *really* delete them until Solr frees its locks from it, which happens while reloading? Thank you for sharing your experiences! Kind regards, Em Alexander Kanarsky wrote: > > Em, > > yes, you can replace the index (get the new one into a separate folder > like index.new and then rename it to the index folder) outside the > Solr, then just do the http call to reload the core. > > Note that the old index files may still be in use (continue to serve > the queries while reloading), even if the old index folder is deleted > - that is on Linux filesystems, not sure about NTFS. > That means the space on disk will be freed only when the old files are > not referenced by Solr searcher any longer. > > -Alexander > > On Sat, Jan 22, 2011 at 1:51 PM, Em <mailformailingli...@yahoo.de> wrote: >> >> Hi Erick, >> >> thanks for your response. >> >> Yes, it's really not that easy. >> >> However, the target is to avoid any kind of master-slave-setup. >> >> The most recent idea i got is to create a new core with a data-dir >> pointing >> to an already existing directory with a fully optimized index. >> >> Regards, >> Em >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Multicore-Relaod-Theoretical-Question-tp2293999p2310709.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > > -- View this message in context: http://lucene.472066.n3.nabble.com/Multicore-Relaod-Theoretical-Question-tp2293999p2312778.html Sent from the Solr - User mailing list archive at Nabble.com.
