[infinispan-issues] [JBoss JIRA] Updated: (ISPN-1329) org.infinispan.loaders.decorators.AsyncStore leads to OutOfMemoryExceptions

[Manik Surtani (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani updated ISPN-1329:
--------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/509


> org.infinispan.loaders.decorators.AsyncStore leads to OutOfMemoryExceptions
> ---------------------------------------------------------------------------
>
>                 Key: ISPN-1329
>                 URL: https://issues.jboss.org/browse/ISPN-1329
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Configuration, Loaders and Stores
>    Affects Versions: 5.0.0.FINAL
>            Reporter: Robert Stupp
>            Assignee: Manik Surtani
>             Fix For: 5.1.0.ALPHA1, 5.1.0.FINAL
>
>
> When I configure
> {code} 
> <async
>     enabled="true"
>     threadPoolSize="3"/>
> {code}
> the implementation creates three threads names "CoalescedAsyncStore" per cache store.
> When adding a large amount of data to the cache (for example indexing a lot of Lucene documents), the application will stop working with a lot of OutOfMemory exceptions.
> This is caused by the implementation of org.infinispan.loaders.decorators.AsyncStore that uses an unbounded LinkedBlockingQueue.
> A lot of worker threads push a huge amount of modifications into the queues, but the underlying cache store is not able to handle throughput.
> As a quick solution change
> {code}
>    private final LinkedBlockingQueue<Modification> changesDeque = new LinkedBlockingQueue<Modification>();
> {code}
> to
> {code}
>    private final LinkedBlockingQueue<Modification> changesDeque = new LinkedBlockingQueue<Modification>(512);
> {code}
> and add a new configuration option to the async element, that specifies the capacity of the Linked Blocking Queue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira