On 10/09/2014 09:10 PM, Sean O'Gorman wrote:
> Hi,
>
> I'm wondering if someone can help me? I am trying to set up a gluster
> cluster and am having issues with the peering process, the primary is
> stuck in 'State: Probe sent to peer (Connected)' and the secondary is in
> the 'Sent and received
As per the subject line, how do I translate a Gluster UUID to a file on
disk? Using iotop I'm seeing a dozen or more (varies somewhat over time)
entries showing:
glusterfsd -s server_name --volfile-id
gluster-rhev.server_name.gluster_brick_1 -p
/var/lib/glusterd/vols/gluster-rhev/run~osix.glu
How can I replace machines in a gluster cluster with triple replication?
I've had crashes and I've replaces single machines before but always
with one with the same name. Now I need to take machine1, machine2, and
machine3 out of the cluster and replace it with machineA, machineB, and
machineC.
Thanks, Ted. I'll try this today.
On Thu, Oct 9, 2014 at 11:11 AM, Ted Miller wrote:
> On 10/7/2014 1:56 PM, Ryan Nix wrote:
>
> Hello,
>
> I seem to have hosed my installation while trying to replace a failed
> brick. The instructions for replacing the brick with a different host
> name/IP
On 10/7/2014 1:56 PM, Ryan Nix wrote:
Hello,
I seem to have hosed my installation while trying to replace a failed
brick. The instructions for replacing the brick with a different host
name/IP on the Gluster site are no longer available so I used the
instructions from the Redhat Storage clas
Hi,
I'm wondering if someone can help me? I am trying to set up a gluster
cluster and am having issues with the peering process, the primary is stuck
in 'State: Probe sent to peer (Connected)' and the secondary is in the
'Sent and received peer request (Connected)' has anyone seen this before?
Any
On 10/9/2014 6:23 AM, Nathan Fiedler wrote:
In the Gluster community documentation, the ZFS Use Case [1]
recommends disabling the ZIL (intent log). Any thoughts on why that
would be the case? Much of the advice on tuning ZFS recommends against
disabling the ZIL, so I'm curious if there is a goo
In the Gluster community documentation, the ZFS Use Case [1] recommends
disabling the ZIL (intent log). Any thoughts on why that would be the case?
Much of the advice on tuning ZFS recommends against disabling the ZIL, so
I'm curious if there is a good reason why it should be done with Gluster.
The
