Hi Qumar,
Cluster name provided in load-balancer xml is only used for creating
cluster view in load-balancer plugin. They need not be physically
present, i.e., cluster with that name may not exist. So for standalone
instances, you can use cluster name as
standalone-instance-<instance-name>. Each standalone-instance must be in
different cluster.
Load-balancer functionality does not change with multiple clusters.
There are some points to keep in mind
1. Clusters can be heterogeneous, i.e., different clusters can have
different set of applications
2. If two or more cluster have same application, then new(non-sticky)
requests for that application will be distributed across instances in
all of those clusters.
3. Fail-over of session is restricted to cluster boundary. Hence
load-balancer restrict fail-over within cluster boundary. It will
fail-over requests to another cluster, if and only if, there are no
healthy instances in cluster. However in such a case, session will be lost.
Thanks,
Kshitiz
glassfish_at_javadesktop.org wrote:
> Hi Kshitiz,
>
> Thanks for your quick response!
>
> You said, "there is no separate element for stand-alone instance. You can use
> <cluster> element to specify the same"
> Does it Mean I can add an extra <cluster> tag in "loadbalancer.xml" and can specify my stand alone application server instances within it?
>
> and if yes, How can I provide a name to this cluster tag as it does not exist [In case I have only stand alone application server instance - no cluster]?
>
> Could you also please provide me some details [links] about the load balance behavior for distributing load if the "loadbalancer.xml" has more than one <cluster> tag?
>
> Thanks again for your help!
>
> Regards,
> Qumar
> [Message sent by forum member 'qumar_samba' (qumar_samba)]
>
> http://forums.java.net/jive/thread.jspa?messageID=324225
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>