Thanks for the ideas.
We are testing out the methods and changes suggested to see if they
work with our current set up, and are checking if the disks are the
bottleneck in this case, but feel free to drop more hints. :)
At the moment we are copying the index at an offpeak hour, but we
would also
Sounds like you might have an I/O issue. If you have multiple partitions /
disks on the searching server you can search from one partition and copy to
another and alternate. If you're using RAID different RAID levels are
optimized for simultaneous reads and writes.
If you have a 3rd machine you
How fast are your disks? Perhaps they are having trouble keeping up with
simultaneous searches and massive file copying.
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Search - Share
- Original Message
From: Chun Wei Ho <[
Hi CW,
You might find this email from Doug Cutting useful, not NFS but using rsync
and hard links ... besides NFS without failover introduces a single point of
faliure.
http://www.mail-archive.com/lucene-user@jakarta.apache.org/msg12709.html
Regards,
Dan
On 4/3/07, Chun Wei Ho <[EMAIL PROTECT
