[Gluster-users] Removing transport type from a volume

[Jon Tegner]

After restarting the services, the error messages disappeared, problem
solved ;-)



/jon


On Sep 17, 2012 10:22 "Jon Tegner" <tegner at renget.se> wrote:

> Thanks!
> 
> 
> 
> 
> We see a lot of errors of the type
> 
> "E [rdma.c:4417:tcp_connect_finish] 0-glusterStore2-client-2: tcp
> connect to failed (Connection refused)"
> 
> These errors do appear on the two servers with infiniband, not on the
> ones without.
> 
> Also, despite this flood of error messages in nfs.log, things appear
> to
> work. Is it safe to ignore this?
> 
> 
> 
> 
> Thanks again,
> 
> 
> 
> 
> /jon
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Sep 17, 2012 08:05 "Vijay Bellur" <vbellur at redhat.com> wrote:
> 
> > On 09/17/2012 12:39 AM, Jon Tegner wrote:
> > > Have a volume consisting of 4 bricks. It was set up using
> > > infiniband
> > > with
> > >
> > > "Transport-type: tcp,rdma"
> > >
> > > Since then the infiniband adapters have been removed from two of
> > > the
> > > servers, and I would like to remove the "rdma-transport-type" from
> > > the
> > > setup.
> > >
> > > Please excuse me if this is a stupid question, but I haven't been
> > > able
> > > to figure out how to achieve this (is it just by removing "rdma"
> > > from
> > > the "volume.brick.mount.vol-files" on the 4 bricks)?
> > >
> >
> > Right now, there is no way to alter the transport type after a
> > volume
> > has been created.
> >
> > If you are interested in preventing mounts to happen over
> > Infiniband,
> > blocking port 24008 on all servers might be an option.
> >
> > -Vijay
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120917/98562f6f/attachment.html>