[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-513) Experiencing long delays when indexing entities saved in different transactions

[Florin Haizea (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37450#action_37450 ] 

Florin Haizea commented on HSEARCH-513:
---------------------------------------

Hi Amin,

In my previous post the Person-Name scenario was just an example that I used to underline the fact that equals and hashCode would just cause hibernate search to skip some of the entities and that was the actual thing that "solved" our bug. The Name object is not present in the code that I added to this jira issue.
The number of people that are added in your project and mine is 7924 (the last id in the test file is "0 @I7924@ INDI"). So the number of documents should match this number. If there are less, that means that not all people are indexed (most likely due to the equals method).

> Experiencing long delays when indexing entities saved in different transactions
> -------------------------------------------------------------------------------
>
>                 Key: HSEARCH-513
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513
>             Project: Hibernate Search
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 3.2.0.CR1
>         Environment: Hibernate 3.5.1-Final
> Spring 3.0.2
> MySQL Connector 5.1.6
>            Reporter: Florin Haizea
>             Fix For: 3.3.0
>
>         Attachments: AllLibsExceptSpringAndHibernate.zip, build.xml, hibernate-search-jms.zip, hibernate3.jar, HibernateSearchJira.zip, output.txt, output08052010.rtf, SpringAndHibernateLibs.zip
>
>
> https://forum.hibernate.org/viewtopic.php?f=9&t=1003224
> I have 3 entities Person, Event and ParentOfBirthEvent. I save about 8000 Person objects in batches of 20, each batch is being saved in a different transaction. After a sufficient number of entities have been persisted (the saving and indexing of initial batches takes between150ms and 500ms) the indexing of the entities that are saved in some of the following batches takes a very large amount of time (sometime even minutes for a whole batch).
> The problem is that in order for these delays to appear there has to be a certain relationship between the objects saved in the current batch and objects saved in previous batches. The only way in which I can reproduce this 100% is by importing a file (which was submitted by one of the users of our app), creating entities based on the data in that file and saving the entities in batches of 20. When I reach batch number 273 or so the indexing starts taking a lot of time.
> If I removed the @IndexedEmbedded annotation from the "parent" field in the ParentOfBirthEvent class the problem is solved. Also, if I removed all the hibernate search listeners from the sessionFactory the problem is solved.

-- 
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