[
https://jira.jboss.org/jira/browse/MODCLUSTER-144?page=com.atlassian.jira...
]
Brett Cave closed MODCLUSTER-144.
---------------------------------
Resolution: Cannot Reproduce Bug
The affinity will be maintained by the cookie on the client, and mod_cluster on the proxy
will direct client to the correct backend server.
Affinity replication between multiple mod_cluster servers
---------------------------------------------------------
Key: MODCLUSTER-144
URL:
https://jira.jboss.org/jira/browse/MODCLUSTER-144
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR1
Environment: ec2 or centos5.4 + apache2.2.3 + JBoss AS 5.1.0.GA
Reporter: Brett Cave
Assignee: Jean-Frederic Clere
mod_cluster maintains affinity (aka session stickiness) between clients and application
servers. However, if scaling up or down number of http / frontend servers running
mod_cluster, a client may be directed to 1 server intitially and then be directed to
another frontend later (depending on connection distribution in front of http servers). If
this occurs, other http servers are not aware of each other's affinity, and so there
is a chance that (if session is not replicated on jboss as servers) a clients session will
be lost if he is migrated to a new http server. This would be particularly applicable in a
cluster consisting of a number of buddy partitions fronted by >1 mod_cluster http
servers.
Not sure about implmentation, but if the mod_cluster.sar service could report relevant
info required to maintain affinity back to all frontend servers, a higher level of fault
tolerance could be achieved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira