[Bugs] [Bug 1241963] New: Peer not recognized after IP address change

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1241963

            Bug ID: 1241963
           Summary: Peer not recognized after IP address change
           Product: GlusterFS
           Version: 3.7.2
         Component: glusterd
          Assignee: kparthas at redhat.com
          Reporter: kparthas at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    jdarcy at redhat.com, kparthas at redhat.com
        Depends On: 1241274
            Blocks: 1241275, 1241904



+++ This bug was initially created as a clone of Bug #1241274 +++

In a user environment, a server might be migrated/restarted with a different IP
address than it had before.  DNS has been updated to point the old name at the
new address, and thus clients can still reconnect to it OK, but other servers
fail to recognize it as a cluster member because of the address change.  In
this particular case, the problem is related to containerization of the
servers, but it can also occur with bare-metal failover solutions.  The key
factor is really that the user is unable/unwilling to configure their routing
so that a floating service address can be reassigned to a new physical machine
in case of failover or migration.

Extra detail: the problem occurs because the *recipient* of a "peer probe"
message initially stores the sender's string-valued IP address instead of its
name.  If we then probe in the other direction using that peer's name, we
update our peer record with that as well, but that's a total hack and doesn't
seem totally foolproof either.  A better solution is to store and subsequently
compare against reverse-resolved host names for probes we receive, whenever
such names are available.  Such an approach would be effectively immune to such
address changes (though it doesn't solve the general problem of DNS errors or
misconfiguration).

--- Additional comment from Anand Avati on 2015-07-08 17:35:17 EDT ---

REVIEW: http://review.gluster.org/11587 (glusterd: use a real host name
(instead of numeric) when we have one) posted (#1) for review on master by Jeff
Darcy (jdarcy at redhat.com)

--- Additional comment from Anand Avati on 2015-07-09 08:48:04 EDT ---

REVIEW: http://review.gluster.org/11587 (glusterd: use a real host name
(instead of numeric) when we have one) posted (#2) for review on master by Jeff
Darcy (jdarcy at redhat.com)

--- Additional comment from Anand Avati on 2015-07-10 08:35:48 EDT ---

COMMIT: http://review.gluster.org/11587 committed in master by Krishnan
Parthasarathi (kparthas at redhat.com) 
------
commit 09b808f008150acb980cdf0cd4f945b57aeb71a0
Author: Jeff Darcy <jdarcy at redhat.com>
Date:   Wed Jul 8 09:52:15 2015 -0400

    glusterd: use a real host name (instead of numeric) when we have one

    Change-Id: Ie9cc201204d3d613e3e585cab066a07283db902c
    BUG: 1241274
    Signed-off-by: Jeff Darcy <jdarcy at redhat.com>
    Reviewed-on: http://review.gluster.org/11587
    Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1241274
[Bug 1241274] Peer not recognized after IP address change
https://bugzilla.redhat.com/show_bug.cgi?id=1241275
[Bug 1241275] Peer not recognized after IP address change
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=blnyjb49L0&a=cc_unsubscribe