Bug 1226923 - Cache async operations should not use the asyncTransportExecutor thread pool
Summary: Cache async operations should not use the asyncTransportExecutor thread pool
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: 6.5.1
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-01 12:53 UTC by Dan Berindei
Modified: 2025-02-10 03:47 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:47:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5518 0 Major Resolved Introduce a separate thread pool for async cache operations 2018-09-06 06:58:28 UTC

Description Dan Berindei 2015-06-01 12:53:58 UTC 
At the moment, it is very easy for an application to start a huge number of putAsync operations and fill the asyncTransportExecutor thread pool, delaying internal work such as state transfer. Increasing the size of the asyncTransportExecutor thread pool won't work, because that would in turn fill the remoteCommandsExecutor 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 a higher number of remoteCommandsExecutor threads than asyncOperationsExecutor threads, avoiding this problem.
Comment 5 Red Hat Bugzilla 2025-02-10 03:47:41 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.