[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-236) Find whether or not indexWriter.optimize() requires an index lock
Sanne Grinovero (JIRA)
noreply at atlassian.com
Thu Oct 23 14:55:05 EDT 2008
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31519#action_31519 ]
Sanne Grinovero commented on HSEARCH-236:
-----------------------------------------
We can't avoid the lock;
It fails even before trying to really optimize: because other threads use the index concurrently, they hold (maybe on turn, but doesn't matter)
the Lucene write lock.
Even if the optimization task could do it's work without a DP lock, it has good chances to hit a timeoutexception:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@/home/sanne/idx/write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:85)
at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:1054)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:698)
at org.hibernate.search.test.optimizer.OptimizeTask.run(OptimizeTask.java:19)
> Find whether or not indexWriter.optimize() requires an index lock
> -----------------------------------------------------------------
>
> Key: HSEARCH-236
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-236
> Project: Hibernate Search
> Issue Type: Task
> Reporter: Emmanuel Bernard
> Assignee: Sanne Grinovero
> Fix For: 3.1.0.Beta2
>
>
--
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list