[Gluster-users] error trying to create replicated volume on EC2
Brandon Simmons
bsimmons at labarchives.com
Tue Sep 13 17:14:47 UTC 2011
I'm not sure I'm doing this right. I have two identical machines, A and B.:
----------------------- CONSOLE -----------------------
A ~$: gluster peer probe domU-BB-BB-BB-BB.compute-1.internal
Probe successful
A ~$: gluster peer status
Number of Peers: 1
Hostname: domU-BB-BB-BB-BB.compute-1.internal
Uuid: 8d5d9af4-6a92-4d56-b063-c8fc9ac17a45
State: Peer in Cluster (Connected)
B ~$: gluster peer status
Number of Peers: 1
Hostname: AA-AA-AA-AA (the IP of host A)
Uuid: 8d5d9af4-6a92-4d56-b063-c8fc9ac17a45
State: Peer in Cluster (Connected)
A ~$: sudo gluster volume create test-vol replica 2 transport tcp
domU-AA-AA-AA-AA.compute-1.internal:/mnt/brick1
domU-BB-BB-BB-BB.compute-1.internal:/mnt/brick1
Brick: domU-AA-AA-AA-AA.compute-1.internal:/mnt/brick1,
domU-BB-BB-BB-BB.compute-1.internal:/mnt/brick1 in the arguments mean
the same
----------------------- CONSOLE -----------------------
After I do the peer probe from server A, server A shows up as a peer
in server B, but it has the same UUID.
What have I done wrong here?
Thanks,
Brandon
More information about the Gluster-users
mailing list