[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-550) Failover targets should be chosen deterministically

[Paul Ferraro (JIRA)]

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

Paul Ferraro commented on MODCLUSTER-550:
-----------------------------------------

[~dmehra] This fix is not applicable to EAP - only to EWS.

> Failover targets should be chosen deterministically
> ---------------------------------------------------
>
>                 Key: MODCLUSTER-550
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-550
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Native (httpd modules)
>    Affects Versions: 1.2.13.Final, 1.3.5.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>             Fix For: 2.0.0.Alpha1, 1.2.14.Final, 1.3.6.Final
>
>
> Under the following conditions:
> 1. A request arrives for a session with an unknown route
> 2. A request arrives for a session with a known route in an error state, or if the intended worker is unresponsive and needs to failover
> ... the failover target must be chosen in a deterministic way.  This is meant to mitigate the situation where concurrent requests failover to different nodes and cause cluster-wide contention for the session.  Given a consistent ordering of workers (e.g. lexographically), the failover target should be chosen by something like: hash code of session id % active worker count.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)