[
https://issues.jboss.org/browse/ISPN-9722?page=com.atlassian.jira.plugin....
]
Will Burns commented on ISPN-9722:
----------------------------------
The big thing to watch out for with CallerRunsPolicy is we don't accidentally run
operations on the wrong thread is more important, such as running a blocking operation on
the CPU thread or CPU operation on the blocking thread pool (although the latter every
once in a while wouldn't be that bad).
Perform all CacheStore operations on a separate thread
------------------------------------------------------
Key: ISPN-9722
URL:
https://issues.jboss.org/browse/ISPN-9722
Project: Infinispan
Issue Type: Enhancement
Components: Loaders and Stores
Reporter: Will Burns
Assignee: Will Burns
Priority: Major
Fix For: 10.0.0.Beta4, 10.0.0.Final
Persistence is one of the few remaining systems that are not non blocking. This needs to
be remedied. We will eventually need to add an SPI that does this, but for now we need to
offload the persistence operations to a different thread pool.
This should only require changes in the PersistenceManager to return non blocking methods
(ie. return CompletionStage). We should then update references to use non blocking when
possible.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)