Hi all,
Using 0.162, I'm having trouble trying to update an index. It's not on
NFS and I call finish() with optimize => 0.
The error is as follows:
Eval failure: Couldn't open file
'/home/roberto/wd/kedin-score/fs_store/indexer/event/_1.del': File
exists at /usr/local/lib/perl/5.8.8/KinoSearch/Store/FSInvIndex.pm line 88
KinoSearch::Store::FSInvIndex::open_outstream('KinoSearch::Store::FSInvIndex=HASH(0x4db8630)',
'_1.del') called at
/usr/local/lib/perl/5.8.8/KinoSearch/Index/DelDocs.pm line 35
(stacktrace omitted)
I can't consistently replicate the error, but it will eventually happen.
The code that updates the index is on a long-running process and the
error can happen any time, sometimes after updating a single record and
others after hours or days.
Searching for a solution I found this in the archive :
http://www.rectangular.com/pipermail/kinosearch/2006-July/000331.html
As it seems this change has not been ported to 0.162, I am now calling
$indexer->_release_locks manually after each call to finish(), but to no
avail. The error keeps happening.
Apart from migrating to 0.20 (can't do at the moment), any advice on how
to duplicate/fix the error or a pointer to any relevant documentation or
mailing list message would be greatly appreciated.
Thanks in advance!
--Roberto
_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch
Using 0.162, I'm having trouble trying to update an index. It's not on
NFS and I call finish() with optimize => 0.
The error is as follows:
Eval failure: Couldn't open file
'/home/roberto/wd/kedin-score/fs_store/indexer/event/_1.del': File
exists at /usr/local/lib/perl/5.8.8/KinoSearch/Store/FSInvIndex.pm line 88
KinoSearch::Store::FSInvIndex::open_outstream('KinoSearch::Store::FSInvIndex=HASH(0x4db8630)',
'_1.del') called at
/usr/local/lib/perl/5.8.8/KinoSearch/Index/DelDocs.pm line 35
(stacktrace omitted)
I can't consistently replicate the error, but it will eventually happen.
The code that updates the index is on a long-running process and the
error can happen any time, sometimes after updating a single record and
others after hours or days.
Searching for a solution I found this in the archive :
http://www.rectangular.com/pipermail/kinosearch/2006-July/000331.html
As it seems this change has not been ported to 0.162, I am now calling
$indexer->_release_locks manually after each call to finish(), but to no
avail. The error keeps happening.
Apart from migrating to 0.20 (can't do at the moment), any advice on how
to duplicate/fix the error or a pointer to any relevant documentation or
mailing list message would be greatly appreciated.
Thanks in advance!
--Roberto
_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch