[hibernate-issues] [Hibernate-JIRA] Closed: (HSEARCH-511) Clean up orphaned lock files on startup
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-511?pag...
]
Sanne Grinovero closed HSEARCH-511.
-----------------------------------
Resolution: Won't Fix
Removing the lock defeats the purpose, if you really want to remove the lock you can
configure a different locking mechanism as explained on [LockFactory
Configuration|http://docs.jboss.org/hibernate/stable/search/reference/en-...]
in the reference.
Selecting *single* for example you would have a fair protection to prevent the MassIndexer
to use the index concurrently to normal work, but in case of a restart the locks would be
gone.
I hope this is a good solution for your case, if you need an explicit API please discuss
it on the mailing list we would like to hear about it.
Clean up orphaned lock files on startup
---------------------------------------
Key: HSEARCH-511
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-511
Project: Hibernate Search
Issue Type: Improvement
Components: engine
Affects Versions: 3.2.0.CR1
Reporter: Marc Schipperheyn
Assignee: Sanne Grinovero
Fix For: 3.3.0
I have had several occassions when the MassIndexer failed to complete for some reason and
I had to restart Tomcat. MassIndexer creates lockfiles for the indexes it is updating.
These lock files remain after a restart and block MassIndexer from running again.
I suggest that Hibernate Search during startup checks for the existence of lock files in
the index directory and removes then if they are there. This prevents an administrator
from having to go and do it manually which is a bummer in production.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira