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

[bugzilla at redhat.com]

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

            Bug ID: 1241904
           Summary: Peer not recognized after IP address change
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: core
          Severity: urgent
          Assignee: rhs-bugs at redhat.com
          Reporter: nsathyan at redhat.com
        QA Contact: annair at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    jdarcy at redhat.com
        Depends On: 1241274, 1241275



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

+++ 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-08 17:36:56 EDT ---

REVIEW: http://review.gluster.org/11569 (glusterd: use a real host name
(instead of numeric) when we have one) posted (#3) for review on release-3.6 by
Jeff Darcy (jdarcy at redhat.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=LdzX8aCr5s&a=cc_unsubscribe