On 2/13/07, Bill Au <[EMAIL PROTECTED]> wrote:
Solr snapshots are created using hard links. The file is not deleted as
long as there is 1 or more
link to it.
Or a process that holds it open. It would work even if there were no
links in the filesystem because the IndexReader would still be hol
Solr snapshots are created using hard links. The file is not deleted as
long as there is 1 or more
link to it.
Bill
On 2/13/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
On 2/13/07, Ken Krugler <[EMAIL PROTECTED]> wrote:
> >A Lucene's IndexReader opens all index files it needs when it is
instant
On 2/13/07, Ken Krugler <[EMAIL PROTECTED]> wrote:
>A Lucene's IndexReader opens all index files it needs when it is instantiated.
>Changes to a Lucene index via IndexWriter never change an existing
>file... new files are always created.
>Put the two together and it allows an IndexWriter (or any
On 2/13/07, Ken Krugler <[EMAIL PROTECTED]> wrote:
Hi all,
In looking at the snapinstaller script, it seems to do the following:
1. Copy a new index directory from the master to the slave's Solr
data directory, giving it a name "index.tmp".
2. Delete the current index directory ("index").
3.
On 2/13/07, Ken Krugler <[EMAIL PROTECTED]> wrote:
Hi all,
In looking at the snapinstaller script, it seems to do the following:
1. Copy a new index directory from the master to the slave's Solr
data directory, giving it a name "index.tmp".
2. Delete the current index directory ("index").
3.
Hi all,
In looking at the snapinstaller script, it seems to do the following:
1. Copy a new index directory from the master to the slave's Solr
data directory, giving it a name "index.tmp".
2. Delete the current index directory ("index").
3. Rename the temp index directory to be "index".
Th
