eplicated to it's replica member.
We seem to be OK but I found it alarming there was no info on this out there.
What would you have done to handle this? Was there a simpler procedure?
Nobodys Home
From: Joe Landman
To: gluster-devel@nongnu.org
Sent: Fri,
Sorry... Gluster 3.1.4 running on CentOS 5.5 using kernel 2.6.38
From: Nobodys Home
To: gluster-us...@gluster.org
Cc: gluster-devel@nongnu.org
Sent: Fri, May 6, 2011 6:48:33 PM
Subject: [Gluster-devel] Gluster "Peer Rejected"
Hello All,
I have
Hello All,
I have 8 servers.
7 of the 8 say that gbe02 is in state State: Peer Rejected (Connected).
gbe08 says it is connected to the other 7 but they are all State: Peer
Rejected
(Connected)
So it would appear that gbe02 is out of sync with the group.
I triggered a manual self heal by doi
All,
Is this a fair summary of the following translators without going to much into
detail?
* cluster/unify is listed as Obsolete/legacy. This has been replaced by
cluster/distribute. Cluster/unify had a single point of failure called the
namespace brick.
* cluster/replicate replaces clus
