[Gluster-users] initial pool setup -- bidirectional probe required?
jaloren at gmail.com
Sat Feb 4 14:03:13 UTC 2017
That's quite interesting. Why does a system with multiple ips make that
necessary? Would you be able to provide an explanation on what the probe is
actually doing and what it is used for? Or alternatively point me to some
documentation that lays this out? Gluster official docs don't seem to
really explore this in any detail from what I could find.
On Sat, Feb 4, 2017 at 4:29 AM, Atin Mukherjee <atin.mukherjee83 at gmail.com>
> You'd not need a bidirectional probe until and unless you want to assign
> multiple IPs/host names to a particular peer.
> On Fri, 3 Feb 2017 at 16:35, Joseph Lorenzini <jaloren at gmail.com> wrote:
>> According to the docs, when you initially set up a gluster storage pool,
>> the first two servers need to probe each other. However, after that, you
>> add additional servers in by probing from a node that's already in the
>> However, when I follow the directions with gluster 3.8, the behavior
>> doesn't seem to match up when I do the initial set up of two nodes. I probe
>> from server 1 to server 2 but I do not probe from server 2 to server 1. My
>> expectation would be that either the pool or peer commands would indicate
>> the server 2 does not "trust" server 1 but it in fact server 2 just
>> indicates its successfully connected in a pool and server 1 is a trusted
>> In addition, if I do a probe from server 2 to server 1, it does not just
>> say probe success. Instead it says, "probe successful host already in peer
>> So here are my questions: is this initial probe each server from the
>> other dance actually required? And if it is, is a there a way to tell
>> through a command or looking at a log whether that's occurred or not?
>> Gluster-users mailing list
>> Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users