No, I wasn't using NFS. It was difficult to make a diagnostic, since we had no access to the file system of the production machine. Since it occured on production only (live on a busy web site), we decided to circumvent the problem by making an alternative implementation that would not use mixed read locks and write locks. So far that solution fares well!
Cheers, Hes. On 10/19/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
This doesn't really sound right ... were you by any chance using NFS (or some other network storage mechanism) in the orriginal implimentation? : So, this turned out not to be stable! After a while (a day or so, or two), : any index would get corrupted, because a segment would disappear. : : I circumvented the problem using seperate indexes for searching and : updating. The search index is copied every ten minutes to accomodate new : search requests. The problem seems to have gone away. : : So here's my tip: if you have continuous updates and a lot of search : requests, use different indexes for searching and for updating! -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
