-
1. Re: Wildfly 10 not load balancing to other host
hfluz Mar 21, 2016 8:20 AM (in response to hfluz)I'm adding my host controller and slave log.
Host controller: master log - Pastebin.com
Slave: slave log - Pastebin.comhttp://pastebin.com/TMZtpt3U
These lines caught my attention:
[Server:backend2] 08:56:58,956 INFO [org.infinispan.CLUSTER] (remote-thread--p7-t1) ISPN000310: Starting cluster-wide rebalance for cache clustering-demo.war, topology CacheTopology{id=1, rebalanceId=1, currentCH=DefaultConsistentHash{ns=80, owners = (1)[master:backend2: 80+0]}, pendingCH=DefaultConsistentHash{ns=80, owners = (2)[master:backend2: 40+40, master:backend1: 40+40]}, unionCH=null, actualMembers=[master:backend2, master:backend1]}
[Server:backend2] 08:56:59,023 INFO [org.infinispan.CLUSTER] (remote-thread--p7-t1) ISPN000310: Starting cluster-wide rebalance for cache routing, topology CacheTopology{id=1, rebalanceId=1, currentCH=DefaultConsistentHash{ns=80, owners = (1)[master:backend2: 80+0]}, pendingCH=DefaultConsistentHash{ns=80, owners = (2)[master:backend2: 40+40, master:backend1: 40+40]}, unionCH=null, actualMembers=[master:backend2, master:backend1]}
[Server:backend2] 08:56:59,376 INFO [org.infinispan.CLUSTER] (remote-thread--p7-t2) ISPN000336: Finished cluster-wide rebalance for cache clustering-demo.war, topology id = 1
It seems to confirm that slave:backend3 is not detected.
-
2. Re: Wildfly 10 not load balancing to other host
rhusar Apr 24, 2016 6:56 PM (in response to hfluz)However, when I accessed the main server, the load was still being balanced only to backend1 and backend2.
Let me just note here that if you are using sticky sessions (which mod_cluster uses by default) the existing sessions will be routed to the same nodes, so you should create new sessions to see if they are load balanced to the 3rd member. This is probably not a problem but just thought I should mention it.
actualMembers=[master:backend2, master:backend1]}
Right, as you say, the backend3 did not join the cluster and neither did it register with the mod_cluster load-balancer since no sessions are routed to it. There can be bunch of issues but its most certainly a misconfiguration on your side. When you say:
instead of adding the 3rd backend server to the same host, I created another host and added the backend3 server to it
do you mean another physical machine? In that case if you be clear that the servers will not be discovered as the nodes are bound to localhost (127.0.0.1).
If not double check your configuration, make sure the app is deployed, port offset is configured, etc...