[Gluster-users] gluster update question regarding new DNS resolution requirement

Erik Jacobson erik.jacobson at hpe.com
Mon Sep 20 15:59:30 UTC 2021

Hello all! I hope you are well.

We are starting a new software release cycle and I am trying to find a
way to upgrade customers from our build of gluster 7.9 to our build of
gluster 9.3

When we deploy gluster, we foribly remove all references to any host
names and use only IP addresses. This is because, if for any reason a
DNS server is unreachable, even if the peer files have IPs and DNS, it
causes glusterd to be unable to reach peers properly. We can't really
rely on /etc/hosts either because customers take artistic licene with
their /etc/hosts files and don't realize that problems that can cause.

So our deployed peer files look something like this:


That is, with full intention, we avoid host names.

When we upgrade to gluster 9.3, we fall over with these errors and
gluster is now partitioned and the updated gluster servers can't reach

[2021-09-20 15:50:41.731543 +0000] E [name.c:265:af_inet_client_get_remote_sockaddr] 0-management: DNS resolution failed on host

As you can see, we have defined on purpose everything using IPs but in
9.3 it appears this method fails. Are there any suggestions short of
putting real host names in peer files?


This supercomputer will be using gluster for part of its system
management. It is how we deploy the Image Objects (squashfs images)
hosted on NFS today and served by gluster leader nodes and also store
system logs, console logs, and other data.



More information about the Gluster-users mailing list