[infinispan-issues] [JBoss JIRA] (ISPN-825) Consider staggering remote get requests when using DIST

[Mircea Markus (JIRA)]

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

Mircea Markus commented on ISPN-825:
------------------------------------

This should also halve the number of OOB threads, see ISPN-2710
                
> Consider staggering remote get requests when using DIST
> -------------------------------------------------------
>
>                 Key: ISPN-825
>                 URL: https://issues.jboss.org/browse/ISPN-825
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: RPC
>    Affects Versions: 4.1.0.Final
>            Reporter: Manik Surtani
>            Assignee: Mircea Markus
>              Labels: optimization, performance
>             Fix For: 5.3.0.Final
>
>
> In DIST mode, when a request is made on a key that is not mapped locally, a remote get is sent to all data owners of that key and the first response is used.  This can add unnecessary load on the network as all nodes still eventually respond, and if values are large this can cause a lot of unnecessary network traffic.
> The purpose of broadcasting to all data owners is so that (1) if one is down, another could still respond (2) if one is overloaded, others may respond faster.
> A solution around this could be based on either (or both) of:
> * Provide a configurable stagger timeout, e.g. 100ms.  E.g., RPC to (random) Owner1.  Wait for timeout t.  If no response, RPC to Owner2.  etc.
> * Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners is 5.
> Needs careful thought and design.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira