Daniel, maybe it is just taking long to detect connection failure. Can you try with 'option transport-timeout 20' (sets response timeout to 20 seconds) in all your protocol/client and see if you still face the 'hang' ? avati 2008/4/3, Daniel Maher <dma+gluster@xxxxxxxxx <dma%2Bgluster@xxxxxxxxx>>: > > On Thu, 03 Apr 2008 09:02:51 +0200 Guido Smit <guido@xxxxxxxxx> wrote: > > > Daniel, > > > > From what I can see, your setup should work. Which version are you > > using? > > > I am using the version which is available in the Fedora 8 repository : > > # glusterfs --version > glusterfs 1.3.8 built on Feb 3 2008 > > It goes without saying that this is a deal-breaker for using Gluster; > if a cluster fails because one of the nodes goes down, i'm going to > have a hard time recommending it as a platform. > > Any and all advice or suggestions on the matter are greatly appreciated. > > > > -- > Daniel Maher <dma AT witbe.net> > > > _______________________________________________ > > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > -- If I traveled to the end of the rainbow As Dame Fortune did intend, Murphy would be there to tell me The pot's at the other end.
