As per the EC2 based deployment implementation we had, the LB to which the elastic IP is mapped becomes the primary LB. This will not be applicable in the new model, and we may have to explicitly specify or have some mechanism for one of the LBs to become the primary. The easier option is, as Sanjiva mentioned, keep all LBs active and do DNS RR.
On Tue, Apr 10, 2012 at 4:39 PM, Nirmal Fernando <[email protected]> wrote: > Hi All, > > Say I have a primary and secondary LBs. How to configure them such that > LBs know each other's existence? > > PS: I know how to configure a single LB, and cluster of other instances. > There we map LB's public IP in axis2.xml of other instances. I tried same > way with 2 LBs, but it failed to build AxisConfig and I think it's not the > correct way. > > -- > > Thanks & regards, > Nirmal > > Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
