[jboss-jira] [JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available

[Dan Berindei (JIRA)]

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

Dan Berindei commented on JGRP-1905:
------------------------------------

Another option I see in Infinispan would be to attach a ResponseFilter to the request and only wait for a response from the nodes that are actually members of the "web" cluster. Actually it would be members of the individual caches, ATM we don't have a way to keep track of which members are part of a fork cluster.

> FORK: RPCs might block if fork channel or fork stack is not available
> ---------------------------------------------------------------------
>
>                 Key: JGRP-1905
>                 URL: https://issues.jboss.org/browse/JGRP-1905
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Critical
>             Fix For: 3.6.2
>
>
> When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out.
> h5. Solution
> * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available").



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