-
1. Re: clustering achieved ?
jbosstcs Feb 17, 2009 6:15 AM (in response to jbosstcs)in continuation of the above architecture what i have now done is separate one m/c from a cluster by changing its PartitionName in cluster-service.xml.... the server logs show appropriate messages indicating the remaining members of the cluster... however failover is still occurring amongst the severs not in cluster... how is that possible ?
-
2. Re: clustering achieved ?
brian.stansberry Feb 17, 2009 9:34 AM (in response to jbosstcs)Apache knows nothing about how you've organized the backend servers beyond what you configure in workers.properties. In workers.properties when you set up a load balancer worker you list the regular workers it should balance requests across. You need to limit that list to the workers that you want to receive requests.
-
3. Re: clustering achieved ?
jbosstcs Feb 17, 2009 10:06 AM (in response to jbosstcs)exactly... apache will not care about how the app servers are arranged... you mean to say that just because the app servers are given in the workers.properties file and load balanced , failover will occur in case one of the constituents goes down ?? why will apache care about the failover part ?
shouldnt that be the headache of the app servers ? -
4. Re: clustering achieved ?
brian.stansberry Feb 17, 2009 11:15 AM (in response to jbosstcs)The load balancer (Apache) is what handles failover. The request comes into apache and it decides how to handle it. If it sees the request's session is associated with a backend server that is no longer available, Apache picks a different server (i.e. fails over). If it passes the request through to a backend server and the request fails with a recoverable problem (e.g. ConnectException connecting to the backend server), it tries a different backend server (i.e. fails over).
-
5. Re: clustering achieved ?
jbosstcs Feb 17, 2009 11:34 AM (in response to jbosstcs)oh... now i get it... but consider the following situation... say i have 2 app servers load balanced by an apache server... after a request has gone to AS1 suppose it goes down... now my question is how does apache know whether AS1 has gone down and route the request to AS2 ( this will not be a case of ConnectException )... i mean this is exactly what i too have observed but i would like to know the reason of the behaviour...
does apache keep a track of the requests ?