Hi Ulrich,
Thank you for letting us know. Glad to hear that your system is back to
normal.
Regards,
Karthik
On Mon, Feb 10, 2020 at 9:51 PM Ulrich Pötter
wrote:
> Hello Karthik,
>
> thank you very much. That was exactly the problem.
> Running the command (cat
>
Hello Karthik,
thank you very much. That was exactly the problem.
Running the command (cat
/.meta/graphs/active/-client-*/private | egrep -i
'connected') on the clients revealed that a few were not connected to
all bricks.
After restarting them, everything went back to normal.
Regards,
Hi Ulrich,
>From the problem statement, seems like the client(s) have lost connection
with brick. Can you give the following information?
- How many clients are there for this volume and which version they are in?
- gluster volume info & gluster volume status outputs
- Check whether all the
Dear Gluster Users,
we are running the following Gluster setup:
Replica 3 on 3 servers. Two are CentOs 7.6 with Gluster 6.5 and one was
upgraded to Centos 7.7 with Gluster 6.7.
Since the upgrade to gluster 6.7 on one of the servers, we encountered
the following issue:
New healing entries
