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).
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)
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)
COMMIT: http://review.gluster.org/11587 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 09b808f008150acb980cdf0cd4f945b57aeb71a0 Author: Jeff Darcy <jdarcy> 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> Reviewed-on: http://review.gluster.org/11587 Reviewed-by: Shyamsundar Ranganathan <srangana> Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user