[Gluster-devel] afr fault recovery

[Krishna Srinivas]

Hi Nathan,

Give this option in client/protocol volume definition:
"option transport-timeout 30"

I think you have given it as 5 minutes (300 secs)

Krishna

On 8/6/07, Nathan Allen Stratton <nathan at robotics.net> wrote:
>
> Attached, this time it actually came back! I shut vs1 down at 10:37:40 and
> vs0 glusterfs came back after about 5 min at 10:42:01.... Any way to not
> lose service on vs0 and vs2 nodes for that long?
>
> ><>
> Nathan Stratton                         CTO, Voila IP Communications
> nathan at robotics.net                  nathan at voilaip.com
> http://www.robotics.net                 http://www.voilaip.com
>
> On Mon, 6 Aug 2007, Krishna Srinivas wrote:
>
> > Can you run glusterfs in the DEBUG mode and send the logs?
> >
> > glusterfs -f client.vol -L DEBUG -l /tmp/glusterfs.log /mnt/gluster
> >
> > can you glusterfs in DEBUG on vs0, kill the glusterfsd on vs1 and
> > mail the /tmp/glusterfs.log?
> >
> > Thanks
> > Krishna
> >
> > On 8/6/07, Nathan Allen Stratton <nathan at robotics.net> wrote:
> > > On Mon, 6 Aug 2007, Krishna Srinivas wrote:
> > >
> > > > Hi Nathan,
> > > >
> > > > Can you confirm that you are not killing the server to which
> > > > the client connects?
> > > >
> > > > According to the spec, client connects to server on 127.0.0.1:6996
> > > > Which server are you running here(vs0/vs1/vs2)? What is the ip address of the
> > > > server you are killing?
> > >
> > > So each server also has a client, so that is why I used loopback. So if I
> > > kill vs0 then server and client for vs0 are down. However clients on vs1
> > > and vs2 also point to each localhost are still up. So they should still be
> > > working, but are locked.
> > >
> > > -Nathan
> > >
> > >
> > > _______________________________________________
> > > Gluster-devel mailing list
> > > Gluster-devel at nongnu.org
> > > http://lists.nongnu.org/mailman/listinfo/gluster-devel
> > >
> >
>