[jboss-jira] [JBoss JIRA] (AS7-4862) Remote EJB SFSB load balancing still suboptimal

Tue Jun 5 09:22:17 EDT 2012

     [ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar reopened AS7-4862:
---------------------------------

This must remain open as it is an issue. I will rephrase the as the cause might be something else, e.g. incorrect handling of notification about members in the cluster.

The balancing by default should give a reasonable balancing of session creation, we have a test for that in the upstream testsuite but only on 2 nodes, so even the balancing might be really broken.

The defaults and default implementation logic MUST be reasonable. We cannot expect users to go on an change every default to get the product working.

The latest job shows the distribution problem in CR1 build as well https://hudson.qa.jboss.com/hudson/job/eap-6x-failover-ejb-ejbremote-undeploy-dist-async/2/

> Remote EJB SFSB load balancing still suboptimal
> -----------------------------------------------
>
>                 Key: AS7-4862
>                 URL: https://issues.jboss.org/browse/AS7-4862
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Radoslav Husar
>            Assignee: jaikiran pai
>             Fix For: 7.1.3.Final (EAP)
>
>
> Looking at the load-balancing again, it seems still wrong. Checking the logs, servers were started *and cluster was formed* ~10 seconds prior to starting the client and load-balancing was roughly: 
> * node perf18: ~50% of sessions
> * node perf19: 0
> * node perf20: 0
> * node perf21: ~50% of sessions
> I let all the session to be created in one minute (not all at once).
> The nodes were also specified in the properties.
> {noformat}
> node perf18
> [JBossINF] 07:01:53,991 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (CacheService lifecycle - 1) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
> node perf19
> [JBossINF] 07:01:53,781 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-19,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
> node perf20
> [JBossINF] 07:01:53,781 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-14,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
> node perf21
> [JBossINF] 07:01:53,780 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-12,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
> controller node
> 2012/05/22 07:02:02:932 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Setting thread count: 2000, was: 0
> 2012/05/22 07:02:53:731 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - All runners (2000) started in 50799 milliseconds
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira