Hi,
I just setup distributed geo replication on my two nodes replica master
glusterfs 3.7.11 towards my single slave node replica and noticed that for some
reasons it takes the hostname of my slave node instead of the fully qualified
domain name (FQDN) and this although I have specified the FQD
Notice it actually tells you to look in the logs on server-ip-2 but you did not
include any logs from that server.
On June 21, 2016 10:22:14 AM PDT, Danny Lee wrote:
>Hello,
>
>We are currently figuring out how to add GlusterFS to our system to
>make
>our systems highly available using scripts.
Hi,
Sorry, the client OS version is CentOS 6.6, not 6.7.
And I find it is not the problem of GlusterFS. It's a kernel problem.
futex_wait() may cause deadlock.
https://groups.google.com/forum/#!msg/mechanical-sympathy/QbmpZxp6C64/nMhNjQPTeLEJ
It just happens on CentOS 6.5. The bug was fixed
Hi,
On my GlusterFS clients when I do a lot of copying within the GlusterFS volume
(mounted as native glusterfs) I get quite a lot of these warning in the log of
my kernel (Debian 8):
[Sat Jun 25 12:18:58 2016] net_ratelimit: 8000 callbacks suppressed
[Sat Jun 25 14:39:39 2016] net_ratelimit: 11
we are planning to expand the current glusterfs cluster. there is one problem.
the nodes in old cluster are installed with centos 6.7. however, new cluster
node are using centos 7.X
we are going to use the same glusterfs version 3.6.7 across these different OS,
and make one single filesystem