[KinoSearch] Re: Internal error: field_num 111 > max_field_num 6

[Matthew Berk]

One additional bit of info. I'm running this under mod_perl (latest),  
with the searcher held in class data. I suspect it's a concurrency  
issue, actually. Any thoughts?

Thanks again,

Matthew



On Jun 11, 2007, at 2:42 PM, Matthew Berk wrote:

> Hi Marvin,
>
> First off, thanks for all your great work with KinoSearch!
>
> I'm running into a little problem that sounds a lot like the once  
> posted here:
>
> http://www.rectangular.com/pipermail/kinosearch/2006-May/000157.html
>
> Specifics:
>
> 	- index has about 15m docs
> 	- using KinoSearch 0.15
> 	- running on Debian (Linux oldev4.sea 2.6.18.5-amd64 #2 SMP Fri  
> Dec 15 12:21:08 PST 2006 x86_64 GNU/Linux)
> 	- the error is repeatable; here's the error:
>
> Internal error: field_num 111 > max_field_num 6 at /site/perl/ 
> perl-5.8.8/site_perl/5.8.8/x86_64-linux/KinoSearch/Index/ 
> TermInfosReader.pm line 92\n 
> \tKinoSearch::Index::TermInfosReader::_scan_enum 
> ('KinoSearch::Index::TermInfosReader=HASH(0x93a730)', '\\x{0}\\x{4} 
> 23843') called at /site/perl/perl-5.8.8/site_perl/5.8.8/x86_64- 
> linux/KinoSearch/Index/TermInfosReader.pm line 64\n 
> \tKinoSearch::Index::TermInfosReader::fetch_term_info 
> ('KinoSearch::Index::TermInfosReader=HASH(0x93a730)',  
> 'KinoSearch::Index::Term=HASH(0x235bc20)') called at /site/perl/ 
> perl-5.8.8/site_perl/5.8.8/x86_64-linux/KinoSearch/Index/ 
> SegReader.pm ETC.
>
> 	- the indexer has 7 spec_fields, 1 of which is not indexed
> 	- the index file has been optimized, and is about 4.1G
>
> I'm going to set K_DEBUG to 1 and see what I can see. Any thoughts?
>
> Thanks,
>
> Matthew
>



Marchex, Inc.
http://www.marchex.com

This email message and any attachments are solely for intended  
recipients, and may contain information that is privileged and  
confidential.  If you are not the intended recipient, any  
dissemination, distribution or copying is strictly prohibited. If you  
believe that you may have received this message in error, please  
immediately notify the sender by replying to this e-mail message.