[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-511) Clean up orphaned lock files on startup
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-511?pag...
]
Emmanuel Bernard commented on HSEARCH-511:
------------------------------------------
I was thinking about two things mainly:
- make sure we release the lock in as much situations as possible (would a finalize
unlocking things help sometimes??)
- possibly offer a cancel() operation that forcefully clear queues and release opened
locks
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
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