Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1226923

Summary: Cache async operations should not use the asyncTransportExecutor thread pool
Product: [JBoss] JBoss Data Grid 6 Reporter: Dan Berindei <dberinde>
Component: InfinispanAssignee: Tristan Tarrant <ttarrant>
Status: CLOSED UPSTREAM QA Contact: Martin Gencur <mgencur>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: jdg-bugs
Target Milestone: ER1   
Target Release: 6.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:47:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.