Suggestion: make sure the NFS lock daemon (lockd) is running on the NFS server.
Peter ----- Original Message ----- From: "Dmitri Ilyin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 03, 2004 1:09 PM Subject: weblogic cluster, index on NFS and locking problem > Hi, > > We run our application on weblogic cluster. the lucene index service > runs on both server in cluster and they both write to one index > directory, shared via NFS. We have experenced a problem with commit.lock > file, that seems not to be deleted and stayed in the index directory, so > we could not start indexing any more becouse lucene could not > create/read commit.lock file. > > I'm not sure what excatly our problem is. It could be NFS problem or it > could be our "usage" problem. We are just starting to use lucene and > could made something wrong. > > We use lucene to index and to search documents. Write/read could be > concurent. > > I saw in the list some messages about problems with lock files on NFS > file system. But i could not realy understand what the problem is. > > How can we improve our solution?? What do we have to do excatly to avoid > problem with stayed commit.lock file??? > > thaks for any advise > > regards > > Dmitri > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
