[
https://issues.jboss.org/browse/MODCLUSTER-100?page=com.atlassian.jira.pl...
]
Michal Babacek closed MODCLUSTER-100.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
load balancing logic doesn't allow manual demo of load-balancing
----------------------------------------------------------------
Key: MODCLUSTER-100
URL:
https://issues.jboss.org/browse/MODCLUSTER-100
Project: mod_cluster
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.0.1.GA
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
Fix For: 1.0.2.GA, 1.1.0.Beta1
the load-balancing logic counts the requests during a while and uses that counter to
balance the requests between the nodes.
the while is 1 second fixed.... Should be a parameter and probably the default value
should be more than one second.
The actual ormula is:
status = lbstatus + (elected - oldelected) * 1000)/bfactor;
lbfactor is received for the node via STATUS.
lbstatus is recalculated every 1 second (that will be a parameter) like status.
elected is the number of time the worker was elected.
oldelected is elected last time the lbstatus was recalculated.
The node with the lowest status is selected.
If you have very few sessions (like a demo by hands) lbstatus is 0 on all the nodes and
only the first nodes are going to be selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)