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

[Matthew Berk]

Would a simple locking mechanism (I know you have one for .2) work to alleviate the problem under mod_perl?

-----Original Message-----
From: kinosearch-bounces+matthew=openlist.com at rectangular.com on behalf of Marvin Humphrey
Sent: Mon 6/11/2007 4:50 PM
To: KinoSearch discussion forum
Subject: Re: [KinoSearch] Re: Internal error: field_num 111 > max_field_num 6
 

On Jun 11, 2007, at 4:32 PM, Matthew Berk wrote:

> 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?

Yes.  KinoSearch isn't thread safe.

The error message you saw suggests that an input stream has gotten  
out of sync.  It's at the wrong place in the file and reading data  
that the module considers insane; there's a sanity check in place to  
give you that exception and head off the looming segfault.

The error from a year ago was due to a 32-bit bottleneck I'd missed  
truncating a file pointer.  Since then, I don't think I've received  
any reports of 0.15 i/o sync errors other than yours.


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



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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 3713 bytes
Desc: not available
Url : http://www.rectangular.com/pipermail/kinosearch/attachments/20070611/b7e64b99/attachment.bin