[
https://issues.jboss.org/browse/MODCLUSTER-178?page=com.atlassian.jira.pl...
]
Radoslav Husar commented on MODCLUSTER-178:
-------------------------------------------
{quote}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.{quote}
If I am reading this right, what you just described are *sticky* sessions and that is how
they currently work.
What this Jira is about are non-sticky sessions (i.e. they do not stick to particular
node) but they do not currently stick to the domain either. Implementing this and enabling
this would keep sessions sticky to the domain only.
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)