ec2 peers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Was a solution to this ever sorted?

I am finding the same thing as Gerry.
Trying the solution below just gives me:

  Probe on host XXXX  port 0 already in peer list

This is on Ubuntu 12.04.2 and gluster 3.3 (this wasn't an issue on
gluster 3.1 I don't recall)


> You can peer probe back from the second server to the first server with DNS
> and it will update itself by figuring out that it is reaching the same UUID.
>
> Avati
>
> On Thu, Jan 20, 2011 at 10:36 PM, Gerry Reno <greno at verizon.net <http://gluster.org/cgi-bin/mailman/listinfo/gluster-users>> wrote:
>
> >/ Question for gluster developers:
> />/
> />/ Could you make the peering so that we can select whether to peer by IP
> />/ or to peer by DNS name?  Or at least make it consistent, all IP or all
> />/ DNS name?
> />/
> />/ Right now even when you try to peer by DNS name, when you check on the
> />/ target server it still shows the source peer with an IP.  We really need
> />/ peering to be by DNS name on both servers when a probe by DNS name is used.
> />/
> />/
> />/ Regards,
> />/ Gerry
> />

-- 
Regards
David



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux