Hey, all. New question: we got a flood of errors last night,
all similar to:
refill: tried to read 1024 bytes, got -1: 5 at
/usr/lib/perl5/site_perl/5.8.5//i386-linux-thread-multi/KinoSearch/Index/FieldsReader.pm
line 54
I suspect this is NFS biting us in the butt. I've been going
over the workaround as described on:
http://www.rectangular.com/kinosearch/docs/devel/KinoSearch/Docs/NFS.html
but in our particular case, switching all the searchers is a
little easier said than done. What we /do/ have is lots of
disk, so I was thinking about:
a) keeping NFS, but don't delete the old .cfs file until
we're sure all the searchers have moved on to the new
.cfs file (a day later, perhaps), or
b) dropping NFS altogether and instead rsyncing the new .cfs
file out, then the segments file, then deleting the old
.cfs file on each searcher host.
Would either of these solutions workaround the issue?
____________________________________________________________
Eamon Daly
NextWave Media Group
Tel: 773 975-1115
Fax: 773 913-0970
all similar to:
refill: tried to read 1024 bytes, got -1: 5 at
/usr/lib/perl5/site_perl/5.8.5//i386-linux-thread-multi/KinoSearch/Index/FieldsReader.pm
line 54
I suspect this is NFS biting us in the butt. I've been going
over the workaround as described on:
http://www.rectangular.com/kinosearch/docs/devel/KinoSearch/Docs/NFS.html
but in our particular case, switching all the searchers is a
little easier said than done. What we /do/ have is lots of
disk, so I was thinking about:
a) keeping NFS, but don't delete the old .cfs file until
we're sure all the searchers have moved on to the new
.cfs file (a day later, perhaps), or
b) dropping NFS altogether and instead rsyncing the new .cfs
file out, then the segments file, then deleting the old
.cfs file on each searcher host.
Would either of these solutions workaround the issue?
____________________________________________________________
Eamon Daly
NextWave Media Group
Tel: 773 975-1115
Fax: 773 913-0970