Gluster users - Sep 2011 - error trying to create replicated volume on EC2

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

Hi Brandon,

Are those 2 cloned instances? If you have cloned B from A after booting it,
then this might have happened. So before cloning remove the /etc/glusterd
directory from A & then clone it.

For the solution, all you need to do is stop glusterd, remove /etc/glusterd
directory from both the machines & then start glusterd again. Now peer probe
should work fine & you can continue with volume creation.

On Tue, Sep 13, 2011 at 10:44 PM, Brandon Simmons
<bsimmons at labarchives.com>wrote:
> 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
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>


-- 
Regards,
Rahul C S
Engineer @ Gluster.
Ph: +919591407901
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20110914/07a02054/attachment.html>