|
I had tried increasing the log level, but didn't find anything of note.
However, after trying a number of different things over the weekend, it turned out that simply starting and stopping the volume seemed to have fixed this.
It does then seem like a bug perhaps, or some confused state, given that it doesn't seem to be any issue with communication between nodes. I'm not really sure how to report it though, given that I don't have steps to reproduce, or much insight into what the
cause might be from logging.
From: Strahil <hunter86_bg@xxxxxxxxx>
Sent: Sunday, October 27, 2019 10:19 AM
To: Timothy Orme <torme@xxxxxxxxxxxx>; gluster-users <gluster-users@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: Re: Remove Brick Rebalance Hangs With No Activity
I guess you can increase loglevel ( check
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3/html/administration_guide/configuring_the_log_level )
Also, have you checked if new and old servers can communicate properly ?
Also consider a tcpdump (for a short time) on the problematic node can prove if communication is OK.
I would go with the logs first.
Best Regards,
Strahil Nikolov
On Oct 26, 2019 20:25, Timothy Orme <torme@xxxxxxxxxxxx> wrote:
Thats what I thought as well. All instances seem to be responding and alive according to the volume status. I also was able to run a `rebalance fix-layout` without any issues, so it seems that communication between the nodes is OK. I also tried replacing
the
10.158.10.1 brick with an entirely new server since that seemed to be the common one between in the logs. Self heal ran just fine in that replica set. However, it still is just hanging on the removal when I try and then remove those bricks.
I might try and full rebalance as well, just to verify that it works.
Only other thing I can think to note is that I'm using SSL for both client and server, and maybe thats obfuscating some more important error message, but it would still seem odd given that other communication between the nodes is just fine.
Any other suggestions for things to try, or other log locations to check on?
Thanks,
Tim
From: Strahil <hunter86_bg@xxxxxxxxx>
Sent: Saturday, October 26, 2019 2:21 AM
To: Timothy Orme <torme@xxxxxxxxxxxx>; gluster-users <gluster-users@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: Remove Brick Rebalance Hangs With No Activity
According to logs there is some communucation problem.
Check that glusterd is running everywhere and every brick process has a pid & port (gluster volume status should point any issues ).
Best Regards,
Strahil Nikolov
On Oct 26, 2019 06:25, Timothy Orme <torme@xxxxxxxxxxxx> wrote:
It looks like this does eventually fail. At a bit of a loss at what to do here... At this point unable to remove any nodes from the cluster. Any help is greatly appreciated!
Here's the log from one of the nodes
[2019-10-26 01:54:35.912284] E [rpc-clnt.c:183:call_bail] 0-scratch-client-4: bailing out frame type(GlusterFS 4.x v1), op(INODELK(29)), xid = 0x38, unique = 0, sent = 2019-10-26 01:24:35.787361, timeout = 1800 for
10.158.10.2:49152
[2019-10-26 01:54:35.912304] E [MSGID: 114031] [client-rpc-fops_v2.c:1345:client4_0_inodelk_cbk] 0-scratch-client-4: remote operation failed [Transport endpoint is not connected]
|
