|
David,
I got you. why i want those ports, because i use LVS with keepalive together,
it can use port 0 in lvs director config , using
#ipvsadm -A -t <vip>:0 -s wrr -p 60
but how to make that happen in keepalive config file?
btw, i agree with your suggestion on glusterfs mount. :)
发自我的小米手机
lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx编写：
>Send lvs-users mailing list submissions to
> lvs-users@xxxxxxxxxxxxxxxxxxxxxx
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.graemef.net/mailman/listinfo/lvs-users
>or, via email, send a message with subject or body 'help' to
> lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
>
>You can reach the person managing the list at
> lvs-users-owner@xxxxxxxxxxxxxxxxxxxxxx
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of lvs-users digest..."
>
>Today's Topics:
>
> 1. Re: Glusterfs native nfs port for LVS (David Coulson)
> 2. Re: Glusterfs native nfs port for LVS (Filipe Cifali)
>
>
>On 3/8/14, 8:31 AM, yang feng电话 wrote:
>> Tomasz,
>> Thanks for your help.
>>
>> I have three gluster nodes, it seems rpc.statd is random port....
>> What I want is to let LVS Loadbalance among those three nodes.
>So why not just make it simple and ignore any tcp/udp ports, and make
>any connection to your VIP forward to the gluster server on the backend.
>Add persistence so connections to different ports from the same client
>IP end up on the same gluster server.
>
>With ipvsadm you can use fwm to manage the rules, then use iptables to
>set the mark in the mangle table. Not sure how your systems are
>configured since you referenced a LVS configuration file, but it is
>doable with the base tools.
>
>
>
>I don't see a reason to put GlusterFS over LVS, since the client already
>loadbalance through the servers.
>
>How you mounted the GlusterFS on the client side?
>
>
>On Sat, Mar 8, 2014 at 10:36 AM, David Coulson <david@xxxxxxxxxxxxxxxx>wrote:
>
>>
>> On 3/8/14, 8:31 AM, yang feng电话 wrote:
>> > Tomasz,
>> > Thanks for your help.
>> >
>> > I have three gluster nodes, it seems rpc.statd is random port....
>> > What I want is to let LVS Loadbalance among those three nodes.
>> So why not just make it simple and ignore any tcp/udp ports, and make
>> any connection to your VIP forward to the gluster server on the backend.
>> Add persistence so connections to different ports from the same client
>> IP end up on the same gluster server.
>>
>> With ipvsadm you can use fwm to manage the rules, then use iptables to
>> set the mark in the mangle table. Not sure how your systems are
>> configured since you referenced a LVS configuration file, but it is
>> doable with the base tools.
>>
>> _______________________________________________
>> Please read the documentation before posting - it's available at:
>> http://www.linuxvirtualserver.org/
>>
>> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
>> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
>> or go to http://lists.graemef.net/mailman/listinfo/lvs-users
>>
>
>
>
>--
>[ ]'s
>
>Filipe Cifali Stangler
>
>
>_______________________________________________
>lvs-users mailing list
>lvs-users@xxxxxxxxxxxxxxxxxxxxxx
>http://lists.graemef.net/mailman/listinfo/lvs-users
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
