So after aborting a index updating session... the readers are running
just fine but all new writers get a
Can't open 'seg_5.ds': File exists at
../c_src/KinoSearch/Store/FSFolder.c:55 kino_FSFolder_open_outstream
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?
-Dan
_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch
just fine but all new writers get a
Can't open 'seg_5.ds': File exists at
../c_src/KinoSearch/Store/FSFolder.c:55 kino_FSFolder_open_outstream
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?
-Dan
_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch