Pedro Ruivo created ISPN-7134:
---------------------------------
Summary: Merge remote-executor thread pool with JGroups thread pool
Key: ISPN-7134
URL:
https://issues.jboss.org/browse/ISPN-7134
Project: Infinispan
Issue Type: Enhancement
Components: Core
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
In current implementation, a message can go through 3 different threads: the receiver
(which reads the data from the socket), the JGroups thread pool (which delivers the
message to Infinispan) and the remote-executor thread pool (which handles the message).
This situation can be improved by merging the remote-executor and JGroups thread pool.
Configuration changes.
{noformat}
<cache-container ...>
<transport remote-command-executor="..." .../>
{noformat}
The default value of {{remote-command-executor}} will change to {{jgroups_thread_pool}}.
So, by default will merge the thread pool
If the user doesn't want to merge the thread pools, it has to configure the thread
pool and change the {{remote-command-executor}} to the configuration name.
{noformat}
<threads>
<blocking-bounded-queue-thread-pool name="my-thread-pool" .../>
</threads>
<cache-container ...>
<transport remote-command-executor="my-thread-pool" .../>
{noformat}
Configure thread pools with name {{jgroups_thread_pool}} will not be allowed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)