Class SimpleFSLockFactory
Implements LockFactory using
NOTE: the javadocs
for File.createNewFile contain a vague
yet spooky warning about not using the API for file
locking. This warning was added due to this
bug, and in fact the only known problem with using
this API for locking is that the Lucene write lock may
not be released when the JVM exits abnormally.
When this happens, a LockObtainFailedException is hit when trying to create a writer, in which case you need to explicitly clear the lock file first. You can either manually remove the file, or use the Unlock(Directory) API. But, first be certain that no writer is in fact writing to the index otherwise you can easily corrupt your index.
If you suspect that this or any other LockFactory is not working properly in your environment, you can easily test it by using VerifyingLockFactory, LockVerifyServer and LockStressTest.
Inherited Members
Namespace:
Assembly: Lucene.Net.NetCore.dll
Syntax
public class SimpleFSLockFactory : FSLockFactoryConstructors
| Name | Description |
|---|---|
| SimpleFSLockFactory() | Create a SimpleFSLockFactory instance, with null (unset) lock directory. When you pass this factory to a FSDirectory subclass, the lock directory is automatically set to the directory itsself. Be sure to create one instance for each directory your create! |
| SimpleFSLockFactory(IO.DirectoryInfo) | Instantiate using the provided directory (as a File instance). |
| SimpleFSLockFactory(String) | Instantiate using the provided directory name (String). |
Methods
| Name | Description |
|---|---|
| ClearLock(String) | |
| MakeLock(String) |