Hi Shankar, On Wed, May 8, 2013 at 9:40 PM, Selvaratnam Uthaiyashankar <[email protected] > wrote:
> > > > On Wed, Apr 17, 2013 at 4:35 PM, Nirmal Fernando <[email protected]> wrote: > >> Hi Sanjeewa, >> >> >> On Wed, Apr 17, 2013 at 4:23 PM, Sanjeewa Malalgoda <[email protected]>wrote: >> >>> Hi Nirmal, >>> I think we need to set host names for entire static service cluster. Let >>> say we have php server cluster and tomcat cluster configuration should be >>> as follows. I believe IP address of the node should be part of node(member) >>> configuration. AFAIK other common static load balancers follow similar >>> pattern. WDYT? >>> >> >> Yes, +1, I missed to address that in the config I sent. We need to have a >> common host name for all the members in the cluster. >> >> >>> What is the plan to distribute load across members(within static >>> cluster) ? Are we using round robin and other algorithms available with >>> synapse or write new algorithm? >>> >> >> Just use RR algorithm provided by Synapse. I'll make them configurable >> via the configuration. >> > > > Hi Nirmal, > > Do you have plans to add FailOver group as well? Or it will be handled as > a different loadbalancing algorithm? > We support basic fail-over mechanism in current algorithm i.e. if a request to a member in a cluster, failed, we'll try to route the request to another member in the cluster, if there're any. If we want some advanced fail-over mechanism, we probably need to implement a new algorithm. > > Shankar > > > >> >> Thanks for the input. >> >>> >>> * cluster1 { * >>> * hosts php.wso2.com, php.private.com* >>> * member1 {* >>> * host 10.1.1.1;* >>> * http_port 80;* >>> * https_port 443; >>> } >>> member2 { >>> host 10.1.1.2; >>> http_port 80; >>> https_port 443; >>> } >>> }* >>> >>> * cluster2 { * >>> * hosts apache.wso2.com, apache.private.com* >>> * member1 {* >>> * host 10.1.1.3;* >>> * http_port 80;* >>> * https_port 443; >>> } >>> member2 { >>> host 10.1.1.4; >>> http_port 80; >>> https_port 443; >>> } >>> }* >>> * >>> * >>> >>> Thanks >>> Sanjeewa >>> >>> On Wed, Apr 17, 2013 at 3:50 PM, Nirmal Fernando <[email protected]>wrote: >>> >>>> Hi All, >>>> >>>> Please suggest syntax for defining $subject. I drafted a possible >>>> config below. >>>> >>>> *loadbalancer.conf* >>>> *==============* >>>> >>>> loadbalancer { >>>> instances 1; >>>> enable_autoscaler true; >>>> # interval between two task executions in milliseconds >>>> autoscaler_task_interval 5000; >>>> # after an instance booted up, task will wait till this much of >>>> time and let the server started up >>>> server_startup_delay 15000; #default will be 60000ms >>>> } >>>> >>>> *#define static members, that are needed to be load balanced >>>> static_members { >>>> #define a new cluster of **static members - name can be any unique >>>> string >>>> cluster1 { >>>> * >>>> * #define a new member >>>> * >>>> * member1 { >>>> * >>>> * #host name of the static member >>>> * >>>> * host abc.com; >>>> * >>>> * # http port of the member >>>> * >>>> * http_port 80; >>>> * >>>> * #https port of the member >>>> * >>>> * https_port 443; >>>> } >>>> member2 { >>>> host abcd.com; >>>> http_port 80; >>>> https_port 443; >>>> } >>>> } >>>> >>>> cluster2 { >>>> member1 { >>>> host xyz.com; >>>> http_port 80; >>>> https_port 443; >>>> } >>>> } >>>> >>>> }* >>>> >>>> services { >>>> defaults { >>>> min_app_instances 1; >>>> max_app_instances 5; >>>> max_requests_per_second 400; >>>> alarming_upper_rate 0.65; >>>> alarming_lower_rate 0.2; >>>> scale_down_factor 0.25; >>>> rounds_to_average 10; >>>> instances_per_scale_up 1; >>>> message_expiry_time 60000; >>>> } >>>> >>>> appserver { >>>> hosts appserver.cloud-test.wso2.com, >>>> as.cloud-test.wso2.com; >>>> domains { >>>> wso2.as.domain { >>>> hosts as2.cloud-test.wso2.com; >>>> min_app_instances 1; >>>> sub_domain worker; >>>> tenant_range *; >>>> } >>>> } >>>> } >>>> } >>>> >>>> -- >>>> >>>> Thanks & regards, >>>> Nirmal >>>> >>>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>>> Mobile: +94715779733 >>>> Blog: http://nirmalfdo.blogspot.com/ >>>> >>>> <http://nirmalfdo.blogspot.com/> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Sanjeewa Malalgoda* >>> WSO2 Inc. >>> Mobile : +14084122175 | +94713068779 >>> >>> <http://sanjeewamalalgoda.blogspot.com/>blog >>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Software Engineer- Platform Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> <http://nirmalfdo.blogspot.com/> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > S.Uthaiyashankar > Director, Cloud Solutions > WSO2 Inc. > http://wso2.com/ - "lean . enterprise . middleware" > > Phone: +94 714897591 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thanks & regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
