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 <jalo...@gmail.com> wrote: > All: > > 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 > pool. > > 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 > peer. > > 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 > list". > > 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? > > > https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Storage%20Pools/ > > Thanks, > Joe > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users -- --Atin
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
