[hibernate-issues] [Hibernate-JIRA] Created: (HSEARCH-222) Entities not found during concurrent update
Sanne Grinovero (JIRA)
noreply at atlassian.com
Wed Jun 25 04:39:21 EDT 2008
Entities not found during concurrent update
-------------------------------------------
Key: HSEARCH-222
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-222
Project: Hibernate Search
Issue Type: Bug
Components: directory provider, engine
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
As we update an entity by deleting it from index by using a database, and afterwards we reinsert it
using an IndexWriter, there is a point in time in the middle were no DPlock is held on the Directory,
At this moment a ReaderProvider could (re)open the index and
all searches performed on this IndexReader will not find the entity at all.
We should use a Read/Write Lock on DP instead of the current ReentrantLock to use a write
lock during index updates and avoid creating a bottleneck for different threads needing a searcher.
--
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