[infinispan-issues] [JBoss JIRA] (ISPN-5083) Hot Rod decoder should use async Cache operations

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052310#comment-13052310 ] 

Dan Berindei commented on ISPN-5083:
------------------------------------

[~rvansa] indeed, async operations will use threads from the transport executor's thread pool, and eventually that thread pool will be full as well. I think the only proper solution is to make the client's socket read timeout higher than the server's replication timeout and lock timeout, so the operation times out on the server side first.

Multiplexing HotRod operations on a single connection is an interesting idea, but it definitely needs its own issue.

> Hot Rod decoder should use async Cache operations
> -------------------------------------------------
>
>                 Key: ISPN-5083
>                 URL: https://issues.jboss.org/browse/ISPN-5083
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Remote Protocols
>            Reporter: Galder Zamarreño
>            Assignee: Gustavo Fernandes
>             Fix For: 7.2.0.Final
>
>
> Hot Rod decoder is currently tying up Netty threads as a result of calling up to Infinispan sync operations. Instead, Hot Rod decoder should call up async operations, convert the Notifying Futures to Scala Futures, and write up the reply when it's received. This should increase performance specially under heavy load.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)