9:44 a.m.
Unlock at startup using SimpleFSLockFactory
-------------------------------------------
Key: HSEARCH-998
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998
Project: Hibernate Search
Issue Type: Bug
Components: massindexer
Affects Versions: 4.0.0.CR2
Environment: Java 1.6, Hibernate Search 4.0.0.CR2 on Oracle Database 10g
Enterprise Edition Release 10.2.0.3.0 - 64bits
Reporter: David Polo
I'm using SimpleFSLockFactory and I'm getting this exception after an unexpected
shutdown of the application during indexation:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out
The workaround consists in executing this code at startup in order to unlock the indexes:
FullTextSession fullTextSession = Search.getFullTextSession(hbSession);
MutableSearchFactory searchFactory = (MutableSearchFactory) fullTextSession
.getSearchFactory();
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
Map<Class<?>, EntityIndexBinder> indexBindingsForEntity = searchFactory
.getIndexBindingForEntity();
for (EntityIndexBinder eib : indexBindingsForEntity.values()) {
IndexManager[] indexManagers = eib.getIndexManagers();
DirectoryBasedIndexManager indexManager = (DirectoryBasedIndexManager)
indexManagers[0];
Directory indexDirectory = indexManager.getDirectoryProvider()
.getDirectory();
if (IndexWriter.isLocked(indexDirectory)) {
IndexWriter.unlock(indexDirectory);
}
}
I have a single application that executes this code at startup so I think it's safe to
unlock the Directory at this time.
I'm doing this because I'm using SimpleFSLockFactory and it leaves write.lock
files.
I need to unlock at startup because I think using NativeFSLockFactory is not an option for
me (I'm using NFS).
It will be a good thing if Hibernate Search have an "unlock at startup" option.
It could be used only in cases like this (not all cases!).
In Solr there is an option:
<unlockOnStartup>true</unlockOnStartup>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:29 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HSEARCH-998) Unlock at startup using SimpleFSLockFactory
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998?pag...
]
David Polo edited comment on HSEARCH-998 at 12/2/11 3:29 AM:
-------------------------------------------------------------
This line is a mistake:
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
I leaved it as a mistake, sorry. I don't know how to edit the issue to erase it.
was (Author: davidpolo):
This line is a mistake:
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
I leaved it as a mistake, sorry.
Unlock at startup using SimpleFSLockFactory
-------------------------------------------
Key: HSEARCH-998
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998
Project: Hibernate Search
Issue Type: Bug
Components: massindexer
Affects Versions: 4.0.0.CR2
Environment: Java 1.6, Hibernate Search 4.0.0.CR2 on Oracle Database 10g
Enterprise Edition Release 10.2.0.3.0 - 64bits
Reporter: David Polo
Labels: hibernate
I'm using SimpleFSLockFactory and I'm getting this exception after an unexpected
shutdown of the application during indexation:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out
The workaround consists in executing this code at startup in order to unlock the
indexes:
FullTextSession fullTextSession = Search.getFullTextSession(hbSession);
MutableSearchFactory searchFactory = (MutableSearchFactory) fullTextSession
.getSearchFactory();
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
Map<Class<?>, EntityIndexBinder> indexBindingsForEntity =
searchFactory
.getIndexBindingForEntity();
for (EntityIndexBinder eib : indexBindingsForEntity.values()) {
IndexManager[] indexManagers = eib.getIndexManagers();
DirectoryBasedIndexManager indexManager = (DirectoryBasedIndexManager)
indexManagers[0];
Directory indexDirectory = indexManager.getDirectoryProvider()
.getDirectory();
if (IndexWriter.isLocked(indexDirectory)) {
IndexWriter.unlock(indexDirectory);
}
}
I have a single application that executes this code at startup so I think it's safe
to unlock the Directory at this time.
I'm doing this because I'm using SimpleFSLockFactory and it leaves write.lock
files.
I need to unlock at startup because I think using NativeFSLockFactory is not an option
for me (I'm using NFS).
It will be a good thing if Hibernate Search have an "unlock at startup" option.
It could be used only in cases like this (not all cases!).
In Solr there is an option:
<unlockOnStartup>true</unlockOnStartup>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:29 a.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-998) Unlock at startup using SimpleFSLockFactory
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998?pag...
]
David Polo commented on HSEARCH-998:
------------------------------------
This line is a mistake:
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
I leaved it as a mistake, sorry.
Unlock at startup using SimpleFSLockFactory
-------------------------------------------
Key: HSEARCH-998
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998
Project: Hibernate Search
Issue Type: Bug
Components: massindexer
Affects Versions: 4.0.0.CR2
Environment: Java 1.6, Hibernate Search 4.0.0.CR2 on Oracle Database 10g
Enterprise Edition Release 10.2.0.3.0 - 64bits
Reporter: David Polo
Labels: hibernate
I'm using SimpleFSLockFactory and I'm getting this exception after an unexpected
shutdown of the application during indexation:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out
The workaround consists in executing this code at startup in order to unlock the
indexes:
FullTextSession fullTextSession = Search.getFullTextSession(hbSession);
MutableSearchFactory searchFactory = (MutableSearchFactory) fullTextSession
.getSearchFactory();
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
Map<Class<?>, EntityIndexBinder> indexBindingsForEntity =
searchFactory
.getIndexBindingForEntity();
for (EntityIndexBinder eib : indexBindingsForEntity.values()) {
IndexManager[] indexManagers = eib.getIndexManagers();
DirectoryBasedIndexManager indexManager = (DirectoryBasedIndexManager)
indexManagers[0];
Directory indexDirectory = indexManager.getDirectoryProvider()
.getDirectory();
if (IndexWriter.isLocked(indexDirectory)) {
IndexWriter.unlock(indexDirectory);
}
}
I have a single application that executes this code at startup so I think it's safe
to unlock the Directory at this time.
I'm doing this because I'm using SimpleFSLockFactory and it leaves write.lock
files.
I need to unlock at startup because I think using NativeFSLockFactory is not an option
for me (I'm using NFS).
It will be a good thing if Hibernate Search have an "unlock at startup" option.
It could be used only in cases like this (not all cases!).
In Solr there is an option:
<unlockOnStartup>true</unlockOnStartup>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 a.m.
New subject: [Hibernate-JIRA] Updated: (HSEARCH-998) Unlock at startup using SimpleFSLockFactory
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998?pag...
]
Sanne Grinovero updated HSEARCH-998:
------------------------------------
Suitable for new contributors: [Yes, likely]
Affects Version/s: (was: 4.0.0.CR2)
Issue Type: New Feature (was: Bug)
Unlock at startup using SimpleFSLockFactory
-------------------------------------------
Key: HSEARCH-998
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998
Project: Hibernate Search
Issue Type: New Feature
Components: massindexer
Environment: Java 1.6, Hibernate Search 4.0.0.CR2 on Oracle Database 10g
Enterprise Edition Release 10.2.0.3.0 - 64bits
Reporter: David Polo
Labels: hibernate
I'm using SimpleFSLockFactory and I'm getting this exception after an unexpected
shutdown of the application during indexation:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out
The workaround consists in executing this code at startup in order to unlock the
indexes:
FullTextSession fullTextSession = Search.getFullTextSession(hbSession);
MutableSearchFactory searchFactory = (MutableSearchFactory) fullTextSession
.getSearchFactory();
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
Map<Class<?>, EntityIndexBinder> indexBindingsForEntity =
searchFactory
.getIndexBindingForEntity();
for (EntityIndexBinder eib : indexBindingsForEntity.values()) {
IndexManager[] indexManagers = eib.getIndexManagers();
DirectoryBasedIndexManager indexManager = (DirectoryBasedIndexManager)
indexManagers[0];
Directory indexDirectory = indexManager.getDirectoryProvider()
.getDirectory();
if (IndexWriter.isLocked(indexDirectory)) {
IndexWriter.unlock(indexDirectory);
}
}
I have a single application that executes this code at startup so I think it's safe
to unlock the Directory at this time.
I'm doing this because I'm using SimpleFSLockFactory and it leaves write.lock
files.
I need to unlock at startup because I think using NativeFSLockFactory is not an option
for me (I'm using NFS).
It will be a good thing if Hibernate Search have an "unlock at startup" option.
It could be used only in cases like this (not all cases!).
In Solr there is an option:
<unlockOnStartup>true</unlockOnStartup>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:39 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HSEARCH-998) Unlock at startup using SimpleFSLockFactory
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998?pag...
]
David Polo edited comment on HSEARCH-998 at 12/2/11 4:37 AM:
-------------------------------------------------------------
This line is a mistake:
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
I left it as a mistake, sorry. I don't know how to edit the issue to erase it.
was (Author: davidpolo):
This line is a mistake:
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
I leaved it as a mistake, sorry. I don't know how to edit the issue to erase it.
Unlock at startup using SimpleFSLockFactory
-------------------------------------------
Key: HSEARCH-998
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-998
Project: Hibernate Search
Issue Type: New Feature
Components: massindexer
Environment: Java 1.6, Hibernate Search 4.0.0.CR2 on Oracle Database 10g
Enterprise Edition Release 10.2.0.3.0 - 64bits
Reporter: David Polo
Labels: hibernate
I'm using SimpleFSLockFactory and I'm getting this exception after an unexpected
shutdown of the application during indexation:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out
The workaround consists in executing this code at startup in order to unlock the
indexes:
FullTextSession fullTextSession = Search.getFullTextSession(hbSession);
MutableSearchFactory searchFactory = (MutableSearchFactory) fullTextSession
.getSearchFactory();
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
Map<Class<?>, EntityIndexBinder> indexBindingsForEntity =
searchFactory
.getIndexBindingForEntity();
for (EntityIndexBinder eib : indexBindingsForEntity.values()) {
IndexManager[] indexManagers = eib.getIndexManagers();
DirectoryBasedIndexManager indexManager = (DirectoryBasedIndexManager)
indexManagers[0];
Directory indexDirectory = indexManager.getDirectoryProvider()
.getDirectory();
if (IndexWriter.isLocked(indexDirectory)) {
IndexWriter.unlock(indexDirectory);
}
}
I have a single application that executes this code at startup so I think it's safe
to unlock the Directory at this time.
I'm doing this because I'm using SimpleFSLockFactory and it leaves write.lock
files.
I need to unlock at startup because I think using NativeFSLockFactory is not an option
for me (I'm using NFS).
It will be a good thing if Hibernate Search have an "unlock at startup" option.
It could be used only in cases like this (not all cases!).
In Solr there is an option:
<unlockOnStartup>true</unlockOnStartup>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:08 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-998) Unlock at startup using SimpleFSLockFactory
[
https://hibernate.onjira.com/browse/HSEARCH-998?page=com.atlassian.jira.p...
]
Emmanuel Bernard commented on HSEARCH-998:
------------------------------------------
How could you differentiate a previous failure from an existing node working protected by
the lock?
Unlock at startup using SimpleFSLockFactory
-------------------------------------------
Key: HSEARCH-998
URL: https://hibernate.onjira.com/browse/HSEARCH-998
Project: Hibernate Search
Issue Type: New Feature
Components: massindexer
Environment: Java 1.6, Hibernate Search 4.0.0.CR2 on Oracle Database 10g
Enterprise Edition Release 10.2.0.3.0 - 64bits
Reporter: David Polo
Labels: hibernate
I'm using SimpleFSLockFactory and I'm getting this exception after an unexpected
shutdown of the application during indexation:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out
The workaround consists in executing this code at startup in order to unlock the
indexes:
FullTextSession fullTextSession = Search.getFullTextSession(hbSession);
MutableSearchFactory searchFactory = (MutableSearchFactory) fullTextSession
.getSearchFactory();
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
Map<Class<?>, EntityIndexBinder> indexBindingsForEntity =
searchFactory
.getIndexBindingForEntity();
for (EntityIndexBinder eib : indexBindingsForEntity.values()) {
IndexManager[] indexManagers = eib.getIndexManagers();
DirectoryBasedIndexManager indexManager = (DirectoryBasedIndexManager)
indexManagers[0];
Directory indexDirectory = indexManager.getDirectoryProvider()
.getDirectory();
if (IndexWriter.isLocked(indexDirectory)) {
IndexWriter.unlock(indexDirectory);
}
}
I have a single application that executes this code at startup so I think it's safe
to unlock the Directory at this time.
I'm doing this because I'm using SimpleFSLockFactory and it leaves write.lock
files.
I need to unlock at startup because I think using NativeFSLockFactory is not an option
for me (I'm using NFS).
It will be a good thing if Hibernate Search have an "unlock at startup" option.
It could be used only in cases like this (not all cases!).
In Solr there is an option:
<unlockOnStartup>true</unlockOnStartup>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:16 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-998) Unlock at startup using SimpleFSLockFactory
[
https://hibernate.onjira.com/browse/HSEARCH-998?page=com.atlassian.jira.p...
]
Sanne Grinovero commented on HSEARCH-998:
-----------------------------------------
I don't think we can differentiate. In fact I don't think we should do this by
default, but having the option would make some people happier.
I wonder though since we now default to using native locks, even a crashed instance should
cleanup the locks. So this is likely not needed anymore?
[HSEARCH-1022]
Unlock at startup using SimpleFSLockFactory
-------------------------------------------
Key: HSEARCH-998
URL: https://hibernate.onjira.com/browse/HSEARCH-998
Project: Hibernate Search
Issue Type: New Feature
Components: massindexer
Environment: Java 1.6, Hibernate Search 4.0.0.CR2 on Oracle Database 10g
Enterprise Edition Release 10.2.0.3.0 - 64bits
Reporter: David Polo
Labels: hibernate
I'm using SimpleFSLockFactory and I'm getting this exception after an unexpected
shutdown of the application during indexation:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out
The workaround consists in executing this code at startup in order to unlock the
indexes:
FullTextSession fullTextSession = Search.getFullTextSession(hbSession);
MutableSearchFactory searchFactory = (MutableSearchFactory) fullTextSession
.getSearchFactory();
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
Map<Class<?>, EntityIndexBinder> indexBindingsForEntity =
searchFactory
.getIndexBindingForEntity();
for (EntityIndexBinder eib : indexBindingsForEntity.values()) {
IndexManager[] indexManagers = eib.getIndexManagers();
DirectoryBasedIndexManager indexManager = (DirectoryBasedIndexManager)
indexManagers[0];
Directory indexDirectory = indexManager.getDirectoryProvider()
.getDirectory();
if (IndexWriter.isLocked(indexDirectory)) {
IndexWriter.unlock(indexDirectory);
}
}
I have a single application that executes this code at startup so I think it's safe
to unlock the Directory at this time.
I'm doing this because I'm using SimpleFSLockFactory and it leaves write.lock
files.
I need to unlock at startup because I think using NativeFSLockFactory is not an option
for me (I'm using NFS).
It will be a good thing if Hibernate Search have an "unlock at startup" option.
It could be used only in cases like this (not all cases!).
In Solr there is an option:
<unlockOnStartup>true</unlockOnStartup>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:36 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-998) Unlock at startup using SimpleFSLockFactory
[
https://hibernate.onjira.com/browse/HSEARCH-998?page=com.atlassian.jira.p...
]
Emmanuel Bernard commented on HSEARCH-998:
------------------------------------------
I was thinking along those lines too. David, what do you think?
Unlock at startup using SimpleFSLockFactory
-------------------------------------------
Key: HSEARCH-998
URL: https://hibernate.onjira.com/browse/HSEARCH-998
Project: Hibernate Search
Issue Type: New Feature
Components: massindexer
Environment: Java 1.6, Hibernate Search 4.0.0.CR2 on Oracle Database 10g
Enterprise Edition Release 10.2.0.3.0 - 64bits
Reporter: David Polo
Labels: hibernate
I'm using SimpleFSLockFactory and I'm getting this exception after an unexpected
shutdown of the application during indexation:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out
The workaround consists in executing this code at startup in order to unlock the
indexes:
FullTextSession fullTextSession = Search.getFullTextSession(hbSession);
MutableSearchFactory searchFactory = (MutableSearchFactory) fullTextSession
.getSearchFactory();
IndexReader indexReader = fullTextSession.getSearchFactory()
.getIndexReaderAccessor().open("");
Map<Class<?>, EntityIndexBinder> indexBindingsForEntity =
searchFactory
.getIndexBindingForEntity();
for (EntityIndexBinder eib : indexBindingsForEntity.values()) {
IndexManager[] indexManagers = eib.getIndexManagers();
DirectoryBasedIndexManager indexManager = (DirectoryBasedIndexManager)
indexManagers[0];
Directory indexDirectory = indexManager.getDirectoryProvider()
.getDirectory();
if (IndexWriter.isLocked(indexDirectory)) {
IndexWriter.unlock(indexDirectory);
}
}
I have a single application that executes this code at startup so I think it's safe
to unlock the Directory at this time.
I'm doing this because I'm using SimpleFSLockFactory and it leaves write.lock
files.
I need to unlock at startup because I think using NativeFSLockFactory is not an option
for me (I'm using NFS).
It will be a good thing if Hibernate Search have an "unlock at startup" option.
It could be used only in cases like this (not all cases!).
In Solr there is an option:
<unlockOnStartup>true</unlockOnStartup>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4496
days inactive
4592
days old
hibernate-issues@lists.jboss.org
7 comments
3 participants
participants (3)
-
David Polo (JIRA) -
Emmanuel Bernard (JIRA)
-
Sanne Grinovero (JIRA)