[Gluster-users] Gluster server and multi-homing, again

Greg_Swift at aotx.uscourts.gov Greg_Swift at aotx.uscourts.gov
Fri Aug 12 15:04:24 UTC 2011

gluster-users-bounces at gluster.org wrote on 08/11/2011 02:22:11 PM:

> On Thu, Aug 11, 2011 at 12:18 PM, Mohit Anchlia
> <mohitanchlia at gmail.com> wrote:
> >> Run one glusterd on server1.  Have "server1-eth1" and "server1-eth2"
> >> refer to the two interfaces.  Use "gluster peer probe server1-eth1"
> >> AND "gluster peer probe server1-eth2" (?)
> >>
> >> My concern is that this will be attempting to add the same server to
> >
> > Don't they have different IP unless I misunderstood your
> > configuration. Are the NIC bonded?
> No, no bonding.  I mean one server with two IP addresses.  So
> "server1-eth1" might be and "server1-eth2" might be
>, but they both connect to the same server (just on
> different interfaces).
> > If you want to try out you will also need to do peer probe with eth1
> > and eth2 IPs.
> If both IPs refer to the same server, they will connect to the same
> glusterd process, unless I find a way to launch two such processes and
> bind each to a separate address...

to clarify... you effectively have 1 server and set of clients, but want
the clients to be able to access the server over both IPs?  With each IP
mapping to only a portion (a brick) of the combined volume?

If I interpreted incorrectly, take the rest with a grain of salt.

I do not think what you want is really possible the way you are describing
it, primarily because gluster uses an algorithm to distribute files across
bricks, thus making targeting a single brick in a volume pretty close to
impossible.  To accomplish that you would need them to be separate volumes.

Once you have them split into separate volumes you can accomplish what you
want (having clients use specific interfaces for specific disks), but it
will require you to not use the recommended mounting method for one of the
two volumes. For the primary interface, you can mount normally from
clients, but for the second one you will have to download the vol file to
the clients and change the IPs in the vol file for the second interface.

we used to do the manual editing.. it was a pain.  we re-worked our system
to allow us to use the default method and it works a lot better.

Although we do still have a failover scenario where we have to do the
manual file change, because gluster doesn't natively support alternate
interface/hostnames in the config file.  hopefully they will one day.


More information about the Gluster-users mailing list