[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-515?pag...
]
Sanne Grinovero updated HSEARCH-515:
------------------------------------
Priority: Critical (was: Major)
Affects Version/s: 3.1.0.GA
3.1.1.GA
3.2.0.Beta1
Component/s: engine
from the logs I saw that some works are applied to the index by a thread which
shouldn't normally write to the index; the thread which is doing this work is the
caller to the Executor, so it means the queue filled up as the strategy applied for
ThreadPools is "caller runs". While "caller runs" is a bug as it might
close the indexWriter to another thread which is still using it, I initially thought it
was a very unusual case, but after writing a quick test I saw that the queue fills up too
fast and I'm able to reproduce the error.
Lucene AlreadyClosedExceptions During Batch Processing With ASYNC
Workers
-------------------------------------------------------------------------
Key: HSEARCH-515
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-515
Project: Hibernate Search
Issue Type: Bug
Components: engine
Affects Versions: 3.1.0.GA, 3.1.1.GA, 3.2.0.Beta1, 3.2.0.CR1
Reporter: j nadler
Priority: Critical
Fix For: 3.2.0
Attachments: HSEARCH-515-reformatted-failing.log
We have a batch job that updates 10,000 preexisting User entities in a single
transaction; each User has an @IndexedEmbedded UserDetails entity which is also updated
during the job run. When run with hibernate.search.worker.execution=sync, life is good.
When we run with async, indexing intermittently fails with a Lucene
AlreadyClosedException. There is no other exception logged even with TRACE logging
enabled.
We did not see this issue with 3.1.1GA but Sanne has noted that it is possible the
exceptions were occurring and were not being logged in that version; I cannot exclude this
possibility.
Posted a log file to
http://www.attensa.com/download/files/attensa.log the first
exception is at timestamp [2010-04-21 11:23:45.992,236829]
Associated forum discussion here:
https://forum.hibernate.org/viewtopic.php?f=9&t=1004022&p=2429214...
--
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