Gluster users - Apr 2020 - never ending logging

On 4/21/20 3:59 PM, Kotresh Hiremath Ravishankar wrote:
> Yes, that's correct. These two xlators are dependent. Initially it was
two different options to enable each xlators to enable ctime feature.
> The consumer had to enable both xlators with two different commands to
enable ctime feature. So it was decided
> to provide the same key "features.ctime" to enable both xlators
internally resulting in two entries in volume info.
Hmm...what about network.tcp-window-size?

Dmitry

Hi all.

We're using 3 nodes Gluster 7.3 (2 + 1 arbiter), yesterday node 2 was
rejected from cluster and I applied following steps to fix :
https://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Administrator%20Guide/Resolving%20Peer%20Rejected/
I also saw
https://docs.gluster.org/en/latest/Troubleshooting/troubleshooting-glusterd/ but
solution isn't compatible as cluster.max-op-version doesn't exist and
all op-version are the same on all 3 nodes.

After renewing SSL certs and several restart all volumes came back online but
glusterd log file on all 3 nodes is filled with nothing else than following 3
lines :

[2020-04-21 13:05:19.478913] I [socket.c:4347:ssl_setup_connection_params]
0-socket.management: SSL support on the I/O path is ENABLED
[2020-04-21 13:05:19.478972] I [socket.c:4350:ssl_setup_connection_params]
0-socket.management: SSL support for glusterd is ENABLED
[2020-04-21 13:05:19.478986] I [socket.c:4360:ssl_setup_connection_params]
0-socket.management: using certificate depth 1

Moreover, I have "Locking failed", "Another transaction is in
progress" and "Error : Request timed out" on gluster volume
status volxxx command.
All SSL certs on clients have also been renewed and all volumes were remounted.
All 3 nodes were alternatively restarted (glusterd) and rebooted.

The cluster is not in production environment but there's about ~250 clients
for ~75 volumes, I don't know how to troubleshoot and fix this problem, if
anyone has an idea.