Mailing List Archive: crash at KinoSearch::InvIndexer::finish

I am using KinoSearch version 0.15. After insert ~175,500 documents, it
crashes at KinoSearch::InvIndexer::finish everytime. Do I need to submit
anything for debugging?

read_bytes: tried to read 7397 bytes, got 0 at
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-mult
i/KinoSearch/Index/NormsReader.pm line 32

KinoSearch::Index::NormsReader::_ensure_read('KinoSearch::Index::NormsReader=HASH(0x9ebd7bc)
') called at
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/KinoSearch/Index/NormsReader.pm
line 25

KinoSearch::Index::NormsReader::get_bytes('KinoSearch::Index::NormsReader=HASH(0x9ebd7bc)')
called at
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/KinoSearch/Index/SegWriter.pm
line
138

KinoSearch::Index::SegWriter::_merge_norms('KinoSearch::Index::SegWriter=HASH(0x99fcf14)',
'
KinoSearch::Index::SegReader=HASH(0x96535b0)',
'KinoSearch::Util::IntMap=SCALAR(0x919126c)') called
at
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/KinoSearch/Index/SegWriter.pm
line 118

KinoSearch::Index::SegWriter::add_segment('KinoSearch::Index::SegWriter=HASH(0x99fcf14)',
'K
inoSearch::Index::SegReader=HASH(0x96535b0)') called at
/usr/lib/perl5/site_perl/5.8.8/i386-linux-th
read-multi/KinoSearch/InvIndexer.pm line 288

KinoSearch::InvIndexer::finish('KinoSearch::InvIndexer=HASH(0x9119958)')
called at src/input
.pl line 92

Thanks

TK
--
Terence Kwan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.rectangular.com/pipermail/kinosearch/attachments/20070823/b046111f/attachment.htm

On Aug 23, 2007, at 12:58 AM, Terence Kwan wrote:

> I am using KinoSearch version 0.15. After insert ~175,500
> documents, it crashes at KinoSearch::InvIndexer::finish everytime.
> Do I need to submit anything for debugging?

Unfortunately, large scale problems can be very difficult to track
down. Certain components of KinoSearch are designed with "dials" on
them so that scaling may be simulated with small data sets, hopefully
cutting down on the number of actual bugs. If I'm going to be able
to help, though, I need a repeatable test case I can debug.

> read_bytes: tried to read 7397 bytes, got 0 at

Maybe you ran out of disk space?

Up until recent devel releases, KS has had very significant index-
time space requirements: sometimes several times final index size.
This was due to the fact that while the final index was compressed,
the temporary files were not. Things should be a lot better now, but
if you wish to stay on the stable branch, you might explore whether
or not a larger disk would help.

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/

_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch