[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-557) Memory leak when using default ReaderProvider with Master/Slave Directories

Johnny B (JIRA) noreply at atlassian.com
Fri Jul 16 03:04:17 EDT 2010


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

Johnny B commented on HSEARCH-557:
----------------------------------

ok .......the adapted directory was just used locally and is not deployed in the test environment. In the test environment we are using HS source for the slave. I adapted the SlaveDirectory in the hope of fast forwarding the problem because of all the wait time to copy over and switch etc etc. 

I upgraded all the apps that use it to the latest versions yesterday and tested it locally over a period of time. On switching over it should no signs of leaking. Im going to release the latest into test and time will tell if it occurs again in our test environment.

For the moment i suggest you close this and if it occurs again with the latest i shall let you know.

Thanks for the support Sanne,
JB

> Memory leak when using default ReaderProvider with Master/Slave Directories
> ---------------------------------------------------------------------------
>
>                 Key: HSEARCH-557
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-557
>             Project: Hibernate Search
>          Issue Type: Bug
>          Components: directory provider
>    Affects Versions: 3.1.0.GA, 3.1.1.GA, 3.2.0.Final
>            Reporter: Sanne Grinovero
>             Fix For: 3.3.0
>
>
> The default ReaderProvider, org.hibernate.search.reader.SharingBufferReaderProvider is keeping a reference to an open index of the most current IndexReader, so it's able to refresh this on demand and track references to previously opened instances.
> The currently open indexReaders for the not-active directory might consume a lot of memory; follows a forum reference where it appears to be a memory leak; still not sure if it's a leak or just needing twice as much memory as otherwise, please comment here.
> https://forum.hibernate.org/viewtopic.php?f=9&t=1005540

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