[Gluster-devel] Can't get afr to work

[James Dyer]

Daniel,

Tried the telnet to port 6997, and the process responded as expected; 
also tried changing the second server volume name to server2, but that's 
made no difference either.

Thanks for trying,

j

On Thu, 8 Mar 2007, Daniel van Ham Colchete wrote:

> James,
> 
> I'm not a Gluster developer but I think I know what the problem is.
> 
> To test my hypothesis, try a telnet at 127.0.0.1:6997. If I'm right it won't
> work.
> 
> The cause of the problem is that the volume name for both servers is the
> same and this shouldn't be right. Try changing the second server volume name
> from 'server' to 'server2'. It's not necessary to change anything else.
> 
> Your gluster mountpoint works because AFR will work even if one of the
> servers is down.
> 
> Tell-me what you found.
> 
> Best regards,
> Daniel Colchete
> 
> On 3/8/07, James Dyer <jad at midentity.com> wrote:
> >
> > I've been trying for ages to get afr to work, but somethings either
> > broken, or I'm just not 'getting it'...
> >
> > I'm running glusterfs 1.3.0-pre2 on RHEL 4
> >
> > At the moment, I'm just trying to get two instances of glusterdfsd running
> > on the same server, with the directories /home/jad/gluster/cfs0 and cfs1
> > respectively.  If I understand things correctly (and it's quite possible
> > I'm not understanding properly), the following configuration should mean
> > that any file I create in the glusterfs directory should appear in both
> > cfs0 and cfs1, due to the replicate option.
> >
> > Configuration for first glusterdfs:
> > volume brick
> >   type storage/posix
> >   option directory /home/jad/gluster/cfs0
> > end-volume
> >
> > volume server
> >   type protocol/server
> >   option transport-type tcp/server
> >   option bind-address 127.0.0.1
> >   option listen-port 6996
> >   subvolumes brick
> >   option auth.ip.brick.allow *
> > end-volume
> >
> > Configuration for second glusterdfs:
> > volume brick
> >   type storage/posix
> >   option directory /home/jad/gluster/cfs1
> > end-volume
> >
> > volume server
> >   type protocol/server
> >   option transport-type tcp/server
> >   option bind-address 127.0.0.1
> >   option listen-port 6997
> >   subvolumes brick
> >   option auth.ip.brick.allow *
> > end-volume
> >
> > Configuration for glusterfs mounting:
> > volume brick
> >   type protocol/client
> >   option transport-type tcp/client
> >   option remote-host 127.0.0.1
> >   option remote-port 6996
> >   option remote-subvolume brick
> > end-volume
> >
> > volume brick-afr
> >   type protocol/client
> >   option transport-type tcp/client
> >   option remote-host 127.0.0.1
> >   option report-port 6997
> >   option remote-subvolume brick
> > end-volume
> >
> > volume afr
> >   type cluster/afr
> >   subvolumes brick brick-afr
> >   option replicate *:2
> > end-volume
> >
> >
> >
> > First instance of glusterdfs run with:
> > glusterfsd -f /home/jad/gluster/server0.vol
> >
> > Second instance:
> > glusterfsd -f /home/jad/gluster/server1.vol
> >
> > glusterfs mount run with:
> > glusterfs -f ./client.vol glusterfs
> >
> >
> >
> > What I'm finding however, is that if I do a 'touch glusterfs/foo.bar', the
> > file is appearing in cfs0, but not in cfs1, which seems to me means that
> > gluster is ignoring my 'option replicate *:2' entry in the afr volume.
> >
> >
> > Any thoughts on what I'm doing wrong???
> >
> > James
> >
> >
> >
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel at nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/gluster-devel
> >
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>