Hi Marvin,
Thanks for the quick reply, here's a fragment of the cfmeta.json file
for the segment:
{
"files": {
"documents.dat": {
"length": "17556716",
"offset": "0"
},
"documents.ix": {
"length": "238760",
"offset": "17556720"
},
"highlight.dat": {
"length": "47793",
"offset": "17795480"
},
"highlight.ix": {
"length": "0",
"offset": "17843280"
},
Not quite sure what the format is but it has a 0 length for
"highlight.ix", highlight.dat has a largish length. Is this some failure
in the highlighting mechansim?
Regards
Edwin
On 08/12/2014 20:32, Marvin Humphrey wrote:
On Mon, Dec 8, 2014 at 12:05 PM, Edwin Crockford <[email protected]> wrote:
Repeatedly get errors like this:
/Can't Seek '/home/ipacs/ipacs/index/webdisk/seg_qjqo/highlight.ix' past EOF
(8 > 0)/
Anybody have and idea what is causing this?
The `highlight.ix` virtual file is a sequence of 8-byte file pointers, each of
which points into a variable size blob in the virtual file `highlight.dat`.
Lucy document numbers for each segment begin at 1, and the length of
`highlight.ix` should be `highest_doc_num * 8`. If the file's length is 0,
that implies that there are no documents in that segment.
The next step when debugging this is to examine the contents of cfmeta.json
for the specific segment. Does the segment really contain no documents? Is
the virtual file `documents.ix`, which follows the same format, also
zero-length?
Marvin Humphrey
