On 10/29/2013 04:12 PM, Robert Hajime Lanning wrote: > On 10/28/13 23:34, B.K.Raghuram wrote: >> The problem I am seeing is this. I am using hostnames to add peers >> into the pool and the output of gluster peer status reflects this. >> However, the output of the --remote-host peer status gives the name of >> the current host in the form of an IP address. Why this discrepancy? > > Was the current host the one you started the cluster from? (ie. you did > peer probe to the other hosts from the current one?) > > If that is the case, this is a known issue. You just need to run peer > probe from a different peer back to the one in question. That will > correct the peer listing. > > As for having the current host in the peer list, a host does not peer > itself, so the context would be incorrect to list it. > > Though, if the current host was not a peer in the cluster, then it would > not list any other peers. > 'gluster pool list' in 3.5 contains information about all nodes in the cluster (including the host on which command is issued). -Vijay
