[Gluster-devel] Testing server down in replicated volume
Pranith Kumar Karampuri
pkarampu at redhat.com
Tue May 29 17:28:32 UTC 2012
I tried this for half an hour, everytime it failed because of readdir. It did not fail in any other fop. I saw that FINODELKs which relate to transactions in afr failed, but the fop succeeded on the other brick. I am not sure why a setattr (metadata transaction) is failing in your setup when a node is down. I will instrument the code to simulate the inodelk failure in setattr. Will update you tomorrow.
Fop failing in readdir is also an issue that needs to be addressed.
----- Original Message -----
From: "Emmanuel Dreyfus" <manu at netbsd.org>
To: "Emmanuel Dreyfus" <manu at netbsd.org>
Cc: gluster-devel at nongnu.org
Sent: Tuesday, May 29, 2012 1:25:09 PM
Subject: Re: [Gluster-devel] Testing server down in replicated volume
On Mon, May 28, 2012 at 07:07:46AM +0200, Emmanuel Dreyfus wrote:
[One server down in a replicated volume]
> /pfs/manu/netbsd/usr/src/sys/sys/siginfo.h:35:54: error:
> /machine/signal.h: Socket is not connected
> Is it the intended behavior?
No reply? I would like to know if I have a NetBSD-specific bug to fix
or if it is standard glusterfs behavior.
manu at netbsd.org
Gluster-devel mailing list
Gluster-devel at nongnu.org
More information about the Gluster-devel