"Simon Wistow" <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 25, 2007 at 05:49:41AM -0400, Michael McCandless said:
> > Ahhh, OK. But do you have a segments_N file?
>
> Yup.
OK, though I still don't understand why the existence of "write.lock"
caused you to lose most of your index on creating a new
On Wed, Jul 25, 2007 at 05:49:41AM -0400, Michael McCandless said:
> Ahhh, OK. But do you have a segments_N file?
Yup.
> Yes, this is perfect. This is the "simple" option I described. The
> more complex option is to use a custom deletion policy which enables
> you to safely do backups (even i
> > The data appears to be there - please tell me that I'm doing something
> > stupid and I can recover from this.
>
> It appears by deleting the write.lock files everything has recovered.
Hmmm -- it's odd that the existence of the write.lock caused you to
lose most of your index. All that should
"Simon Wistow" <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 25, 2007 at 05:19:31AM -0400, Michael McCandless said:
> > It's somewhat spooky that you have a write.lock present because that
> > means you backed up while a writer was actively writing to the index
> > which is a bit dangerous because if th
On Wed, Jul 25, 2007 at 05:19:31AM -0400, Michael McCandless said:
> It's somewhat spooky that you have a write.lock present because that
> means you backed up while a writer was actively writing to the index
> which is a bit dangerous because if the timing is unlucky (backup does
> an "ls" but bef
On Wed, Jul 25, 2007 at 10:08:56AM +0100, me said:
> The data appears to be there - please tell me that I'm doing something
> stupid and I can recover from this.
It appears by deleting the write.lock files everything has recovered.
Is this best practice? Have I just done something so terribly wr
"Simon Wistow" <[EMAIL PROTECTED]> wrote:
> We were affected by the great SF outage yesterday and apparently the
> indexing machine crashed without being shutdown properly.
Eek, sorry! We are so reliant on electricity these days
> I've taken a backup of the indexes which has the usual smat
