[Pacemaker] Configure simple Network Load-balancing
David Coulson
david at davidcoulson.net
Fri Nov 30 14:55:44 UTC 2012
You probably want to direct that question to the iptables mailing list.
On Nov 30, 2012, at 9:54 AM, Ratko Dodevski wrote:
> Can someone tell me how CLUSTERIP works? Because from what I can see, a get all the connections to one server and after some time all the connections go to other server etc... Is it something wrong with my configuration or that's the way it's working?
>
> Thanks and regards
>
>
> On Fri, Nov 30, 2012 at 1:36 PM, David Coulson <david at davidcoulson.net> wrote:
> I would add HA to your existing HA config - The primary issue you have right now is that if tomcat is down, broken or needs to be disabled you don't have a good way of doing that automatically.
>
> My implementations for this type of application are pacemaker + ldirectord + LVS. Since you have a 15x increase in number of clients, now is a good time to argue the business case for something more robust than CLUSTERIP.
>
> David
>
>
> On 11/30/12 7:30 AM, Ratko Dodevski wrote:
>> Probably, but HA is already the solution in place so I have to use-it. Now there are around 200 clients but it will grow up till 3000 in the next two months. Servers have Tomcat installed on them, so basically I need to load balance connections from outside to the Tomcat.
>>
>> Regards
>>
>>
>> On Fri, Nov 30, 2012 at 1:19 PM, David Coulson <david at davidcoulson.net> wrote:
>> All the connections, from how many clients?
>>
>> You might be better off using LVS for this.
>>
>> David
>>
>>
>> On 11/30/12 7:15 AM, Ratko Dodevski wrote:
>>> Hi guys, I need some help on configuring NLB for my application servers. I've installed tomcat on 4 servers and I've decided to use Linux HA for Network Load Balancing, but is seems like all the connections are going only to one of the servers (app-node-1). Can someone tell me what I'm doing wrong? It's pretty simple config, just one clone resource (IPaddr2) running on all nodes. Also, can someone tell me how is NLB done? based on source IP, IP hash or... I need Round Robbin NLB.
>>>
>>> app-node-1:/ # crm configure show
>>> node app-node-1
>>> node app-node-2
>>> node app-node-3 \
>>> attributes standby="on"
>>> node app-node-4
>>> primitive tomcat_ip ocf:heartbeat:IPaddr2 \
>>> params ip="X.X.X.X" cidr_netmask="24" nic="eth0" \
>>> op monitor interval="30s" \
>>> meta target-role="started"
>>> clone nlb_ip tomcat_ip \
>>> meta globally-unique="true" clone-max="4" clone-node-max="1"
>>> property $id="cib-bootstrap-options" \
>>> dc-version="1.1.2-2e096a41a5f9e184a1c1537c82c6da1093698eb5" \
>>> cluster-infrastructure="openais" \
>>> expected-quorum-votes="4" \
>>> stonith-enabled="false" \
>>> no-quorum-policy="ignore" \
>>> last-lrm-refresh="1333954979"
>>> rsc_defaults $id="rsc-options" \
>>> resource-stickiness="100"
>>>
>>> ============
>>> Last updated: Fri Nov 23 01:57:49 2012
>>> Stack: openais
>>> Current DC: app-node-1 - partition with quorum
>>> Version: 1.1.2-2e096a41a5f9e184a1c1537c82c6da1093698eb5
>>> 4 Nodes configured, 4 expected votes
>>> 1 Resources configured.
>>> ============
>>>
>>> Online: [ app-node-1 app-node-4 app-node-2 ]
>>> OFFLINE: [ app-node-3 ]
>>>
>>> Clone Set: nlb_ip (unique)
>>> tomcat_ip:0 (ocf::heartbeat:IPaddr2): Started app-node-1
>>> tomcat_ip:1 (ocf::heartbeat:IPaddr2): Started app-node-2
>>> tomcat_ip:2 (ocf::heartbeat:IPaddr2): Started app-node-4
>>> tomcat_ip:3 (ocf::heartbeat:IPaddr2): Stopped
>>>
>>>
>>> Thanks and regards
>>>
>>> --
>>> Ratko
>>>
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>>
>>> Project Home: http://www.clusterlabs.org
>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs: http://bugs.clusterlabs.org
>>
>>
>>
>>
>> --
>> Ratko
>
>
>
>
> --
> Ratko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20121130/8ca25024/attachment.htm>
More information about the Pacemaker
mailing list