[Gluster-users] Server side or client side AFR
my.whitelion at gmail.com
Tue Apr 26 13:32:52 UTC 2011
Hi, I think that to use the server side AFR is more correct put in front
of a server gluster an LVS Machine (Linux Virtual Server) to balance the
client load, or use, on all AFR server, a protocol like carp (UCARP)
that expose a single IP address for gluster all servers, so the client
will always be connected to the server online.
Il 23/04/2011 07:34, Liam Slusser ha scritto:
> Problem with server side AFR is you loose your redundancy in the event
> that one of your server goes down because the client is only
> connecting to one of the two servers. So if your client is connected
> to the server that went down, you're SOL.
> On Fri, Apr 22, 2011 at 4:05 PM, Nobodys Home <n1shome at yahoo.com> wrote:
>> Hello all,
>> I prefer server side AFR for my topology and I think it makes overall sense
>> for most configurations. However, I don't think the
>> 3.1 documentation regarding the creation of a replicated distributed volume
>> is server side after a bit of testing. It seems like I'm in a bit of a
>> 1. Can I "only" expand volumes on the fly if I use the gluster cli to
>> initially define my volumes?
>> 2. Most of the examples regarding server side AFR "do not show" how to add
>> bricks to a predifined server.vol configuration on the fly. If there is a
>> way to do this can I get help on this?
>> Best Regards,
>> Nobodys Home
>> Gluster-users mailing list
>> Gluster-users at gluster.org
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users