[
https://issues.jboss.org/browse/MODCLUSTER-178?page=com.atlassian.jira.pl...
]
Roman Jurkov commented on MODCLUSTER-178:
-----------------------------------------
this ticket could be simple, however can become tricky if we want to expand this
functionality.
use case one is where we stick to a node (which is supported as we already know)
second use case stick to a domain (which is what this ticket describes)
third use case (which would be tricky i think) is to support combination of both
!cluster-small.png!
first we stick to a node, then in case of a failure of that node we failover to another
node within same domain, and only in case of a second node failure, we will send request
to Domain2.
do you think we would ever want to implement third use case?
i was looking into implementing this one.
Domains: non sticky requests should be contained within a given
domain
----------------------------------------------------------------------
Key: MODCLUSTER-178
URL:
https://issues.jboss.org/browse/MODCLUSTER-178
Project: mod_cluster
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Jean-Frederic Clere
Attachments: cluster-small.png, cluster.jpg
If we have a couple of domains, then non-sticky requests can go to *any* server in *any*
domain.
It would be nice if we could at least make the domain sticky, so e.g. non-sticky requests
always pick the same domain, as long as there are servers in that domain.
Maybe this should be a new flag, e.g. stickyDomain. If stickySession is false, then
we'd check stickyDomain.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)