dmarkham at gmail
Sep 9, 2008, 11:45 AM
So after aborting a index updating session... the readers are running
cleaning up after a failed update..
just fine but all new writers get a
Can't open 'seg_5.ds': File exists at
at build_index.pl line 12
So i have played around a bit and removed all the seg_5.* files and
things seem to correct itself.
I'm sure that is screwing up something...
How should it act after a failure of a writer?
How should i recover from this type of failure?
KinoSearch mailing list
KinoSearch [at] rectangular