[infinispan-issues] [JBoss JIRA] (ISPN-5518) Introduce a separate thread pool for async cache operations

[Dan Berindei (JIRA)]

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

Dan Berindei updated ISPN-5518:
-------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/3519


> Introduce a separate thread pool for async cache operations
> -----------------------------------------------------------
>
>                 Key: ISPN-5518
>                 URL: https://issues.jboss.org/browse/ISPN-5518
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Configuration, Core
>    Affects Versions: 7.2.2.Final, 8.0.0.Alpha1
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 8.0.0.Alpha2
>
>
> At the moment, it is very easy for an application to start a huge number of putAsync operations and fill the transport executor's thread pool, delaying internal work such as state transfer. Increasing the size of the transport executor's thread pool won't work, because that would in turn fill the remote commands and JGroups' OOB thread pools, with the same effect.
> If the cache async operations used a different thread pool, it would be possible to configure more {{remoteCommandsThreadPool}} threads than {{asyncOperationsThreadPool}} threads, avoiding this problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)